[question] remove magisk modules without TWRP on Oreo? - Xiaomi Mi A1 Questions & Answers

Hello guys,
I had been using Magisk & Xposed on Nougat before Oreo rolled out in December. However after update I lost root. When I flashed patched_boot.img I got stuck in bootloop (So I returned to stock boot.img). I am pretty sure bootloop was caused by some incompatible Magisk module. The problem is that I don't know how to disable them now - I don't want to install TWRP (because I want to be able to get OTAs) and when I use only "bootable" version of TWRP, it can not detect any files/partitions, so I am unable to use "mount-magisk.zip" to remove wrong Magisk modules. So I am kind of stuck.
Here is what I want to achieve:
- remove incompatible magisk modules
- gain root without permanent TWRP
- profit
I have been searching this forum for quite a while but couldn't find some relevant consistent information. Any tips how to deal with this?
At the moment I am running Oreo /w January update.
Thank you

For others looking for similar answers, I was able to solve it:
I flashed TWRP, then using "mount-magisk" removed all modules, then using MiFlashTool flashed original rom (you can do that without loosing data) and then I just followed guide to root using patched boot.img.
Good luck
gexcube said:
Hello guys,
I had been using Magisk & Xposed on Nougat before Oreo rolled out in December. However after update I lost root. When I flashed patched_boot.img I got stuck in bootloop (So I returned to stock boot.img). I am pretty sure bootloop was caused by some incompatible Magisk module. The problem is that I don't know how to disable them now - I don't want to install TWRP (because I want to be able to get OTAs) and when I use only "bootable" version of TWRP, it can not detect any files/partitions, so I am unable to use "mount-magisk.zip" to remove wrong Magisk modules. So I am kind of stuck.
Here is what I want to achieve:
- remove incompatible magisk modules
- gain root without permanent TWRP
- profit
I have been searching this forum for quite a while but couldn't find some relevant consistent information. Any tips how to deal with this?
At the moment I am running Oreo /w January update.
Thank you
Click to expand...
Click to collapse

Related

I am rooted, but not happy with my current state

Hey everyone,
I`m running LineageOS on my phone and am rooted using SuperSU which seems to work, according to Rootchecker and the feww apps I use, which make use of root privileges.
But I`m not entirely happy with my current situation, since it seems that more and more apps don`t tend to work with my rooted phone. So what are my ways out of this?
Can I easily unroot my phone, while keeping LineageOS?
Is there a working alternative to SuperSU, which would enable me to stay rooted on LineageOS without reflashing the OS and use Banking-Apps?
I`ve heard of Magisk, but I am unsure of how to switch over from my current state and I`am not sure whether or not it would solve my problems
Thanks for any help in advance!!
Magisk
You just have to go to SuperSU, then Full Unroot, then download Magisk 13.3 and flash it from TWRP. After that you should have Magisk Manager, if for some weird reason you don't, install it via apk
Then you just go to the settings, tick MagiskHide, then go back and open the side panel, MagiskHide - select the apps that you want Magisk to hide itself from
So I tried to do what you said.
I did the full unroot in the SuperSu App,
My phone rebooted
I shut it down again and booted into recovery
Tried flashing Magisk
But it failed, apparently due to my Boot image being patched by another program and told me to go with stock image
What do I do now? And will I lose any data by doing so? Thank you so much for any help!
Weird, but you can simply dirty flash LineageOS (the same one that you have now, or an update, doesn't matter) and it should let you install Magisk.
I did what you said and installed a delta update using LineageOS Downloader. Had to manually flash it in TWRP since I had no root permissions anymore. But I was able to install Magisk like a charm! Now I have to questions:
1. How do I update Magisk? Using the app?
2. Do I have to flash it again everytime I'm updating LOS?
Thanks for the great help so far!
And what exactly are those moduls? Should I be messing with them?
If updates come they will appear on the status bar and you can download them, and they'll install with the phone on. after that you have to (not quick) reboot your phone.
and about the modules, seriously? what do you think??

Some experience after upgrading to Oreo (root)

Hi all,
Not even sure I'm in the right place, still I'd like to share my own experience after upgrading to Oreo last few days. So moderators, if you guys find this irrelevant, or it is in the wrong place, please help me move it accordingly.
I am using XZ F8332. Last few days I decided to say hello to Oreo after some time being patient with the pretty annoying "Upgrade your system" notification. I finally managed to have a fully working Oreo + DRMfix + Magisk + SafetyNet passed and root. Unfortunately good things usually come with bad things too...
At first, I was trying to patch my boot image using ta_poc method. Believe me ta_poc seems to be working on Oreo too, I got all the DRM functionalities working thanks to munjeni & serajr. However, it doesn't seem to be working with both Magisk and SuperSU. I tried all recent versions of those two e.g. Magisk v14, Magisk v14.5 beta, SuperSU v2.79 SR3, SuperSU v2.82 SR5, etc... ALL cause bootloops! I had to come to a conclusion that any methods that patch your modified (with ta_poc) boot image will cause bootloops. There's one thing I didn't try: SuperSU system mode which installs to /system. What's the point of system-less then? But it's up to you to try this.
The above means you are most likely gonna lose root if you go with ta_poc on Oreo. So I had to give ta_poc up and go with DRMfix instead. I got into a few troubles then.
I was initially trying to keep my userdata intact, so I didn't do a full wipe, I actually wiped everything except only my userdata (including data in sdcard). DRMfix didn't fix at all. All I got was only "FIDO_KEYS: Provisioned", the rest was "general error!" and of course DRM functionalities didn't work. I did some search, followed some guides saying about removing these directories: /data/credmgr, /data/drm and /data/mediadrm. There's even a script named "SafetyNet-Cleaning-Tools" also does exactly the same. Perhaps I wasn't that lucky enough. It just didn't work. Until I had to pull all of my data out, do a FULL WIPE including userdata, DRMfix worked then.
Next thing is to get Magisk (or SuperSU) working to have root. I knew recent update of SuperSU causes Xperia devices into bootloops. I also used Magisk on Nougat too. Why not now? So I flashed Magisk v14. Uh oh... I met my old dear friend again, Mr. Bootloops. So Magisk v14 doesn't work on Oreo. But v14.5 beta does. That's how I got it fully working.
Then I pushed my data back to sdcard (including a nandroid of course), did a restore DATA ONLY in TWRP and manually delete the folders mentioned above. After phone started, everything went back. I smiled.
Some existing Magisk modules started to work without any problems. But some other they need busybox. Without any thoughts, I immediately installed osm0sis' busybox installer, the one on Magisk repo. Weirdly it said "Magisk is not activated". I tried other modules, same issue. So only existing modules work, I couldn't install any new modules using Magisk Manager. "Use TWRP then" I thought. I went to TWRP and flashed the busybox installer. My old dear friend came and said "Hi! Bootloops!!" to me again. This time I used Magisk uninstaller to clear magisk files and re-flashed it again. I was able to get back in. I tried YashdSaraf's busybox universal installer. Same issue. Maybe I haven't tested well enough or maybe I went completely wrong way, but looks like busybox isn't working on Oreo? Also, I'm not sure this is the right way to do it, or we have to "clean install" Magisk too? Like uninstall everything first and re-install module by module all over again?
Also, after some Magisk uninstalls and reflashs, suddenly my DRMfix was no longer working. It displayed "general error!" in Service tests -> Security. I tried to fastboot the modified boot image again. Not working. There's no way to get it back except a FULL WIPE. I didn't get it. System-less approach is supposed to have nothing to do with our files. Somehow it does leave some traces, which we need a FULL WIPE to get rid of it? Maybe it isn't just the 3 folders mentioned above, there's maybe more?
Additionally, on Oreo I got some other bad stuffs:
- Adaptive brightness keeps adjusting, going darker and brighter very very quickly. It's no doubt an Oreo's bug.
- Cannot open Titanium Backup. It crashes right after you open it. I tried v8.0 and v8.1. Same issue. Maybe it's because busybox isn't installed?
- I have a feeling battery drains issue comes back. Looks like its consuming more battery than latest Nougat I'm not sure. Haven't got time to do some stats yet.
Last but not least. When I was pulling / pushing data to / from, I noticed that the storage space somehow changed! My phone is 64gb but the second time I got it fully working, it said "storage is 80% full..." and when I opened Settings -> Storage it showed only 21gb! What I did to get it fixed was to run fastboot format userdata. Then I let the phone start normally (without old data), after finishing setup, I turned off and went to TWRP to restore DATA ONLY. Problem solved. I got my storage back. But I have never figured out why. Maybe something wrong with adb pull / push in recovery?
If you've read down this far, I hope my experience could somehow help you avoid encountering the problems that I did.
Me personally I think I will go back to Nougat and stay low for a while. You understand why. Another reason is I also wanna try the "official" xposed for nougat for a little more. rovo89 is freaking awesome. man, he's a legend.
References:
I used this tool to patch my boot image (kernel). This tool origins by tobias.waldvogel but I used the "unofficial" one here and here modified by serajr for the ta_poc method. Thank you guys for this amazing tool.
Magisk latest versions here
SuperSU v2.82 SR5, v2.79 SR3
SuperSU System Mode v2.82 SR5 here
osm0sis' Busybox installer here
YashdSaraf's Busybox universal installer here
Special thanks to serajr, juanpirulo, munjeni, rovo89 and tobias.waldvogel for your amazing works & supports. I dont tag you guys here coz I dont wanna bother you guys
Been there... I feel like that phone don't want to work with poc and Magisk...
FakeMobile said:
Been there... I feel like that phone don't want to work with poc and Magisk...
Click to expand...
Click to collapse
ta poc needs to be rebuild, but munjeni probably dont wanna work in his tool anymore. But serajr´s tool works well so you can root xz oreo with magisk. cheers
Yeah it what I have atm, but I still can't mirror cast to my tv because it not real drm keys

Magisk hell resolved??!!!!!!!??!!!!!!!!!!??

im new at thisxda stuff but i am 90 percent sure i figured out how to keep magisk from uninstalling after a reboot... YOU MAY NEED TO UNINSTALL MAGISK AND ALL MODULES BEFORE DOING THIS USING MAGISK UNINSTALLER basically you have to also install an older version of supersu and it has to be an aroma installer and install as SYSTEM also make a backup of the boot.img just incase you get bricked if you install the supersu app it will say su binary occupied but install should stay install supersu aroma (2.78v2) from https://forum.xda-developers.com/attachment.php?attachmentid=3879523&d=1474248173 before and possibly after magisk install...only tested with magisk 16.2 beta channel and regular install not patched boot on Axon 7 with RR 8.1 weekly 6.0.0 20180225 (us variant) but should work on others probably...let me know how this goes for you
TRY AT OWN RISK I AM NOT RESPONSIBLE FOR DEVICE BOOTLOOPS OR BRICKS
If anyone has a better way to get magisk to hold after a few restarts please let me know
sidenote:this supersu does work with magisk not installed and definately keeps root
(stock boot.img is in initial zip for custom rom) select intall imgs in twrp and flash the boot partition as needed)
ALSO YOU CAN ALWAYS DIRTY FLASH CUSTOM ROM same build or higher IF ALL GOES TO **** AND WONT LOOSE APPS OR DATA AT LEAST ON RR
works for me without problems after last 2 years on any Rom.
dont know what you doing wrong?!
I cant get to bypass safetynet V: other than that root works fine
J0nhy said:
I cant get to bypass safetynet V: other than that root works fine
Click to expand...
Click to collapse
this actually fixed sn for me without the fix installed
Ever tried magisk v15.3? I never had problems with uninstalling, but everything above 15.3 won't pass safety net,at least for me/on stock nougat b10 rom.
desu1337 said:
Ever tried magisk v15.3? I never had problems with uninstalling, but everything above 15.3 won't pass safety net,at least for me/on stock nougat b10 rom.
Click to expand...
Click to collapse
Maybe on stock roms...it should work on l8r versions tho...
try this already https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
also cant have xposed installed with the sn fix

Update to oos 11 and keep root

Hey lads, i wanted to update to oos 11 and keep magisk root, I saw a video tutorial on how to do that but on a previous oos update.
By installing the update without rebooting and installing magisk on inactive slot after OTA.
This sadly didn't work for me so now I am stuck without root access on oos 11.
Do I need to reflash magisk boot.img again or could there be another way to enable it?
Flashing boot.img will delete all my data and apps and I would really hate installing all that again one by one manually...
Any tips on what I can do?
Thanks.
XxSUPRAxX said:
Hey lads, i wanted to update to oos 11 and keep magisk root, I saw a video tutorial on how to do that but on a previous oos update.
By installing the update without rebooting and installing magisk on inactive slot after OTA.
This sadly didn't work for me so now I am stuck without root access on oos 11.
Do I need to reflash magisk boot.img again or could there be another way to enable it?
Flashing boot.img will delete all my data and apps and I would really hate installing all that again one by one manually...
Any tips on what I can do?
Thanks.
Click to expand...
Click to collapse
1. It didn't work, because you took the wrong magisk version. Latest canary or beta works great with A11. I did it myself without issues.
2. There is only one way to get root. Patch the boot.img and flash it.
3. And no, flashing boot.img won't delete anything!
Kollachi said:
1. It didn't work, because you took the wrong magisk version. Latest canary or beta works great with A11. I did it myself without issues.
2. There is only one way to get root. Patch the boot.img and flash it.
3. And no, flashing boot.img won't delete anything!
Click to expand...
Click to collapse
Ohhh.. Thanks! I just realized that it wasnt boot.img that would delete my files as you said, and have now updated to oos 11 with magisk and safeteynet passed. Thanks.
I have a guide for this in the guides section..step by step.
For others with the same question and find this thread instead of the guide: Switch to beta update channel in magisk -> download and install OTA without rebooting -> magisk flash to inactive slot -> reboot & enjoy
Like I said, I have a guide for this.
https://forum.xda-developers.com/oneplus-8-pro/how-to/root-uk-eu-patched-magisk-boot-img-t4175033
Read before you commit.. It's easy..

How to hide root?

I am trying to install hide root as some apps are refusing to run due to phone being rooted.
Is Magisk the only way to hide root? Cause I have removed magisk previously and now I am trying to install it back. However, can I know what version works with ZE552KL? I am using last official firmware from ASUS on this phone.
I can't seems to find any thread about magisk for this phone. I do not want to flash to latest magisk Appreciate any help on this matter.
Ignore this. I have bigger problem.

Categories

Resources