Database Develop

How to? MAGISK for Oreo Exynos

I failed similar times to root my phone with twrp 3.2.xx and 3.1.xx. I used Odin 3 v3.13.1.
Any ideas or thread links for the young padawan?
I appreciate your advice masters :good:

Using Odin Flash TWRP latest from the note 8 TWRP thread here on XDA, one on their site is not latest.
Install magisk manager app from play store.
Download magisk from the app.
Reboot to TWRP and flash the magisk file just downloaded.
Reboot and check magisk manager for root and hide.
Should be good.

Nope. Not working and still ends in a bootloop and it's unable to mount the internal storage.
Something went wrong, so.. my phone is unable to boot the system after that!

The issue is the version of TWRP and Oreo, its not yet compatible on this device, it needs porting over
If you want MAGISK you need to do it all in one hit.
Flash TWRP
Select Read Only Option.
Format Data
Reboot Recovery
Flash the DM Verify Encrypt file
Reboot Recovery, You could be able to flash files wihtout a Data mount error.
Now flash the files you want, i..e MAGISK
Once you have booted the ROM and return back to TWRP you are unable to mount Data.
This can cause various issue when flashing files

Funny you.. How can I format if the internal storage isn't able to mount?
"Select Read Only Option.
Format Data" <-- seems like a contradiction to format a missing
partition.
I think we need to wait until someone will port the twrp for Oreo. cheerio!

Because it needs to be done when you first flash it.
Once you have flash Oreo, Then TWRP, You boot into TWRP and format. You then Flash the DM Verify.
Data is accessible, its empty but accessible, Flashing any files like MAGISK work without any errors.
I have it all working on mine without any issues, I do know if i need to flash any additional files it wont work properly due to Data no longer mountable.
There is a updated version of TWRP that fixes this, but its not been ported over.

Magisk Module causing freeze at boot

I have a Moto x4 running android 8.1 Oreo with November security patches and magisk v18. Stock recovery and rom. I tried installing a couple magisk modules and the phone won't boot with magisk patched boot image installed. I have restored the stock boot image backup and the phone will run without magisk. I have erased magisk manager's cache, and even uninstalled magisk manager, but the modules are still installed and if i use fastboot boot patched_boot.img it won't boot. My system is encrypted and when I boot the TWRP bootable, I am unable to flash or delete anything outside of the user data or my SD card. I cannot install any zip including magisk manager for recovery or magisk core mode only module. I have tried everything I know to do and then some. Any input or assistance would be greatly appreciated. I would like to avoid resetting my data if possible.
Basically, I think I need to delete magisk.img from my system, but I cannot find it anywhere in my system partition using twrp's file browser. Also, I no longer have root access so I cannot adb root and adb shell into it.

Magisk image is in /data/adb. If you have access to /cache, create a file there named ".disable_magisk" (without quotation marks and with the leading dot). That'll enable Core Only Mode.
https://www.didgeridoohan.com/magis...agisk_functionality_bootloop_loss_of_root_etc

Didgeridoohan said:
Magisk image is in /data/adb. If you have access to /cache, create a file there named ".disable_magisk" (without quotation marks and with the leading dot). That'll enable Core Only Mode.
https://www.didgeridoohan.com/magis...agisk_functionality_bootloop_loss_of_root_etc
Click to expand...
Click to collapse
unfortunately, both the /data/adb and /cache are encrypted and inaccessible without root.
That is great to know for the future though, thanks

I got it to work. I needed to use the newest twrp bootable image in order to decrypt the data in recovery. Once this was done, I was able to erase magisk.img with no issues at all. Thanks for all the help.

Bootloop

Hi, my device reboot after I unlock it, I only have access to my Internal memory of my phone via PC
how to unistall/disable magisk so I can delete the modules?
Is there a folder that I can delete?
I don't have TWRP

albysprx said:
Hi, my device reboot after I unlock it, I only have access to my Internal memory of my phone via PC
how to unistall/disable magisk so I can delete the modules?
Is there a folder that I can delete?
I don't have TWRP
Click to expand...
Click to collapse
How you got magisk to work without flashing it?
PoochyXXX

PoochyX said:
How you got magisk to work without flashing it?
PoochyXXX
Click to expand...
Click to collapse
with patched the boot img of my firmware with magisk manager and then I flashed it with fastboot

albysprx said:
with patched the boot img of my firmware with magisk manager and then I flashed it with fastboot
Click to expand...
Click to collapse
Ohhhhh.... Root is very particular without a custom recovery to get your phone to that exact working state it was in before if you had a custom recovery there could of been a couple modules you could use
PoochyXXX

You can always flash a stock boot image. That will disable Magisk completely, but has the drawback of leaving you without root...
To disable or uninstall modules without removing Magisk you would have to have access to /cache (place a file named .disable_magisk, with the leading dot, in /cache and Core Only Mode will be enabled) or /data/adb (delete the Magisk image file) through recovery. Usually not an option on a stock recovery... If there is no custom recovery for your device you might not have many options, but if there is one available and you don't want to install it, you could at least boot it with "fastboot boot recovery <name_of_recovery_file>".

Didgeridoohan said:
You can always flash a stock boot image. That will disable Magisk completely, but has the drawback of leaving you without root...
To disable or uninstall modules without removing Magisk you would have to have access to /cache (place a file named .disable_magisk, with the leading dot, in /cache and Core Only Mode will be enabled) or /data/adb (delete the Magisk image file) through recovery. Usually not an option on a stock recovery... If there is no custom recovery for your device you might not have many options, but if there is one available and you don't want to install it, you could at least boot it with "fastboot boot recovery <name_of_recovery_file>".
Click to expand...
Click to collapse
Yeah, I got working again with flashing the stock boot.img but after flashed again the pacthed boot.img my phone bootloop again...
I tried to install TWRP and got it working, I typed /cache/.disable_magisk in terminal and rebooted and the device works, went to magisk manager and no modules was there, disabled core magisk and the device bootloop again...
now I'm trying to reinstall the entire firmware and make a factory reset before reinstalling magisk...
Should this remove modules installed?

Didgeridoohan said:
You can always flash a stock boot image. That will disable Magisk completely, but has the drawback of leaving you without root...
To disable or uninstall modules without removing Magisk you would have to have access to /cache (place a file named .disable_magisk, with the leading dot, in /cache and Core Only Mode will be enabled) or /data/adb (delete the Magisk image file) through recovery. Usually not an option on a stock recovery... If there is no custom recovery for your device you might not have many options, but if there is one available and you don't want to install it, you could at least boot it with "fastboot boot recovery <name_of_recovery_file>".
Click to expand...
Click to collapse
Yeah, I got working again with flashing the stock boot.img but after flashed again the pacthed boot.img my phone bootloop again...
I tried to install TWRP and got it working, I typed /cache/.disable_magisk in terminal and rebooted and the device works, went to magisk manager and no modules was there, disabled core magisk and the device bootloop again...
now I'm trying to reinstall the entire firmware and make a factory reset before reinstalling magisk...
Should this remove modules installed?

albysprx said:
Yeah, I got working again with flashing the stock boot.img but after flashed again the pacthed boot.img my phone bootloop again...
I tried to install TWRP and got it working, I typed /cache/.disable_magisk in terminal and rebooted and the device works, went to magisk manager and no modules was there, disabled core magisk and the device bootloop again...
now I'm trying to reinstall the entire firmware and make a factory reset before reinstalling magisk...
Should this remove modules installed?
Click to expand...
Click to collapse
If you got the device booting (in Core Only Mode) and still have root you could just use a file explorer, navigate to /sbin/.magisk/img and delete the offending module directories. Or, you could delete the Magisk image file in recovery (it's in /data/adb). Either of those options would remove the modules.

Didgeridoohan said:
If you got the device booting (in Core Only Mode) and still have root you could just use a file explorer, navigate to /sbin/.magisk/img and delete the offending module directories. Or, you could delete the Magisk image file in recovery (it's in /data/adb). Either of those options would remove the modules.
Click to expand...
Click to collapse
Got my device working again in magisk core only mode but the folder /sbin/.magisk/img is empty .-.

albysprx said:
Got my device working again in magisk core only mode but the folder /sbin/.magisk/img is empty .-.
Click to expand...
Click to collapse
Now that you have your device running, do a complete uninstall from the Magisk Manager and start over. That should remove everything...

Didgeridoohan said:
Now that you have your device running, do a complete uninstall from the Magisk Manager and start over. That should remove everything...
Click to expand...
Click to collapse
ok I deleted the magisk.img from data/adb/magisk, did a complete unistall from magisk manager (after the unistall the phone reboot to the TWRP without doing anything), sideloaded the magisk unistaller and got "ERROR: 1", after that I rebooted, rebooted again in recovery mode and installed magisk, rebooted, removed the core mode and rebooted again..
It works!!
Thanks a lot

The root permission request is no longer displayed

I have the root with Magisk in Android 8.0. At first, the warning always came out asking if you wanted to grant root rights to the application that you just opened. However, this warning is no longer displayed, even though the configuration of Magisk Manager is configured in this way.
In the Magus Superuser section, I do not see any trace of the applications that I can not 'root'.
I have updated Magisk Manager, but the error continues. I also removed BusyBox, but the error continues.
I can not give root permission to any other application. But the mobile is rooted, since the first applications that I installed that require root continue to function normally. I can even deactivate the root and then activate it again.
Reinstalling the applications is not solved. With Dalvik and Caché wipe either.
That could be happening? How is it solved?
____
Magisk Manager has all the permissions of everything (memory, background, manual battery mode). I have tried to reinstall Magisk Manager and nothing.
Deactivating BusyBox (Magisk module) and Xposed and restarting still does not work.
Returning to install the Magisk image by TWRP or Fastboot is not fixed either.
I have removed all the fret that I had done to the phone (BusyBox, Xposed, root Magisk and boot modified for the root) and the problem has not been solved. I do not know what may be happening. I do not have other rare applications.
I have installed Device Control and the TWRP application. I have not gotten the root request to skip (although it has activated that option in Magisk Manager).
Definitely, it is not the fault of the new applications, which was the first question I wanted to solve.
Magisk version:
19.3 (19300)
And from Manager 7.2.0 (213), although I have also tried 7.3.2 (224).
The root is done with patching (via Magisk) of RAMDISK.IMG.
I understand that some applications are not compatible with systemless. But I'm not going any of the new ones that I'm trying. Interestingly, other applications compatible with Magisk (except those that installed the first days of the mobile) do not work either.
I have installed Magisk Manager 7.0.0 (and also 6.1.0), but the bug is still there. It seems that it does not depend on the APK.
As my Magisk file to root consists of a patch of RAMDISK.IMG created directly from Magisk Manager I do not know how to create one based on a lower version (for example, version 18.1). It only gives me the option to patch with the latest Magisk Manager version (if I have a lower one, it asks me to update the APK).
Whenever I generate the IMG of my patched RAMDISK.img it is based on 19.3.
How could I generate a patched IMG based on a lower version?
I have microG, not the GApps. Could that influence? Does Magisk need them?

@rovo89

@topjohnwu

https://www.didgeridoohan.com/magisk/MagiskHelp

I have added much more information.

Reinstall firmware???

LoneWolfz said:
Reinstall firmware???
Click to expand...
Click to collapse
I'm going to do it today. Will I lose data if I install SYSTEM.img via Fastboot?

535iu said:
I'm going to do it today. Will I lose data if I install SYSTEM.img via Fastboot?
Click to expand...
Click to collapse
No maybe but i suggest you to backup all your data etc. just to be safe

Seeking a solution to disable Zygisk from ADB or recovery

After enabling Zygisk, my device (LG V20 with Xposed Framework, AlphaOmega rom, MK2000 kernel, etc.) hangs on the boot animation. Unfortunately, I neglected to turn off encryption after my most recent attempt, so I cannot uninstall Magisk through TWRP like before.
Because the device cannot reach the locker, I also cannot unlock it in order to turn off the pin/encryption. I tried to run "magisk --sqlite 'update settings set value=1 where [key]="zygisk"'" from ADB shell, but was told that "root is required for this operation."
Is there any way to turn off Zygisk (or uninstall Magisk completely) from within ADB, fastboot, or TWRP, or has Magisk completely hosed my device at this point?

Bill720 said:
After enabling Zygisk, my device (LG V20 with Xposed Framework, AlphaOmega rom, MK2000 kernel, etc.) hangs on the boot animation. Unfortunately, I neglected to turn off encryption after my most recent attempt, so I cannot uninstall Magisk through TWRP like before.
Because the device cannot reach the locker, I also cannot unlock it in order to turn off the pin/encryption. I tried to run "magisk --sqlite 'update settings set value=1 where [key]="zygisk"'" from ADB shell, but was told that "root is required for this operation."
Is there any way to turn off Zygisk (or uninstall Magisk completely) from within ADB, fastboot, or TWRP, or has Magisk completely hosed my device at this point?
Click to expand...
Click to collapse
if you can flash the original boot img of your rom in fastboot you'll be able to remove magisk

I made some progress on this.
jons99 said:
if you can flash the original boot img of your rom in fastboot you'll be able to remove magisk
Click to expand...
Click to collapse
boot1.img or boot2.img?

both I guess?
why you have 2 boot imgs?

jons99 said:
both I guess?
why you have 2 boot imgs?
Click to expand...
Click to collapse
No idea. I don't even know if they're valid anymore, since I'm on a custom rom and kernel. It's been years since I've installed this stuff, so I don't remember the specifics.

you know what you can do instead is just fastboot boot into your unrooted boot ing and open the magisk app disable zygisk and reboot this way you'll keep magisk

I made some progress on this. Somehow, the device is now bootable again, but Magisk will now not install from (any version of) the app or from recovery. TWRP still can't run the uninstaller because it thinks that the device is encrypted, even though I did remove the pin code.

Bill720 said:
I made some progress on this. Somehow, the device is now bootable again, but Magisk will now not install from (any version of) the app or from recovery. TWRP still can't run the uninstaller because it thinks that the device is encrypted, even though I did remove the pin code.
Click to expand...
Click to collapse
you don't need to run the uninstaller just change the .apk at the end of the magisk app to .zip and flash it in twrp

jons99 said:
you don't need to run the uninstaller just change the .apk at the end of the magisk app to .zip and flash it in twrp
Click to expand...
Click to collapse
That's what I did to get here. It installs from there, (despite the fact that TWRP asks for a password now) but the Magisk app still doesn't recognize it.

Bill720 said:
That's what I did to get here. It installs from there, (despite the fact that TWRP asks for a password now) but the Magisk app still doesn't recognize it.
Click to expand...
Click to collapse
if you have an old kernel you might need to flash an older version of magisk try v23 maybe

jons99 said:
if you have an old kernel you might need to flash an older version of magisk try v23 maybe
Click to expand...
Click to collapse
These results are with version 23.

ok try to see if you have an old backup of your boot partition that's already patched with magisk and try to restore it (make a backup of your existing boot partition first)

jons99 said:
ok try to see if you have an old backup of your boot partition that's already patched with magisk and try to restore it (make a backup of your existing boot partition first)
Click to expand...
Click to collapse
Not sure that I would've taken one of those.

well you can always patch the boot img with magisk and flash it in fastboot that always works

Bill720 said:
After enabling Zygisk, my device (LG V20 with Xposed Framework, AlphaOmega rom, MK2000 kernel, etc.) hangs on the boot animation. Unfortunately, I neglected to turn off encryption after my most recent attempt, so I cannot uninstall Magisk through TWRP like before.
Because the device cannot reach the locker, I also cannot unlock it in order to turn off the pin/encryption. I tried to run "magisk --sqlite 'update settings set value=1 where [key]="zygisk"'" from ADB shell, but was told that "root is required for this operation."
Is there any way to turn off Zygisk (or uninstall Magisk completely) from within ADB, fastboot, or TWRP, or has Magisk completely hosed my device at this point?
Click to expand...
Click to collapse
Try this:
Turn device off
Open ADB command line
Type adb wait-for-device shell magisk --remove-modules
Connect device to USB cable and boot
This should remove modules allowing a successful boot with root.
Did you post this question on Reddit? I just answered an identical question there yesterday lol

jons99 said:
well you can always patch the boot img with magisk and flash it in fastboot that always works
Click to expand...
Click to collapse
Where could I procure a clean boot.img file? Is that part of the rom, the kernel, or something else?

usually it's inside payload.bin from within the rom zip

jons99 said:
usually it's inside payload.bin from within the rom zip
Click to expand...
Click to collapse
Interesting. I extracted the AlphaOmega Rom .zip, and found no payload.bin, but there is a boot.img file in the "kernel" folder. Should I still use that, even if I don't use the kernel supplied with the rom?

you can always use fastboot boot instead of fastboot flash and just boot to this patched boot img you created and see if it works if not a reboot will remove it

jons99 said:
you can always use fastboot boot instead of fastboot flash and just boot to this patched boot img you created and see if it works if not a reboot will remove it
Click to expand...
Click to collapse
I'll have to try that next. Now, if I could just find a working fastboot driver for this device...