Database Users

Anyone get Magisk working on B25?

Just upgraded from B19 to B25 via DrakenFX's zips, and it looks like Magisk has stopped working. I've tried uninstalling and re-installing the zip, but it looks like the superuser app just crashes after prompting for permission. Magisk thinks there's root, but its logs just end with "phh: starting su daemon." (And, of course, safetynet fails). I'd upload a screenshot, but I can't . I'm trying to use Magisk v10.3-beta2 with 17 me.phh.superuser cm-su topjohnwu.
Anyone figured this out, or found another way to get Android Pay working with an unlocked bootloader?
Thanks!

Apparently there is no functional Magisk for stock nougat. You can use 10.2 on MM or 12 on one of the custom (non stock based) nougat roms.

Actually, I did manage to get Magisk 10.3-beta2 working on B19 nougat, so I assumed that it'd work on B25. Looks like that's not the case, though.

That version of Magisk works for me on b25. Three green lights. What version of Magisk manager are you using? I have 4.3.3.

StickMonster said:
That version of Magisk works for me on b25. Three green lights. What version of Magisk manager are you using? I have 4.3.3.
Click to expand...
Click to collapse
Care to share the version of Magisk you have working?

Actually, looks like Magisk 12 works well enough to hide the bootloader on B25, which is all I really wanted, anyways .

lukanite said:
Actually, looks like Magisk 12 works well enough to hide the bootloader on B25, which is all I really wanted, anyways .
Click to expand...
Click to collapse
I want to run magisk so I can use android pay, I'm rooted, on stock nougat, unlocked BL. I've found very little axon 7 specific threads, so just wondering are there any gotcha's? Is it like TWRP where you need a version built for the phone?
thanks

If you're rooted already, I'm not sure if Magisk 12 is going to work, since Magisk Hide only hides MagiskSU. I'd try looking into the guide for Magisk 13, starting from no root, which might be able to get you root with Android Pay

lukanite said:
If you're rooted already, I'm not sure if Magisk 12 is going to work, since Magisk Hide only hides MagiskSU. I'd try looking into the guide for Magisk 13, starting from no root, which might be able to get you root with Android Pay
Click to expand...
Click to collapse
Hey, thanks for getting back. Actually I ended up removing supersu, flashing stock boot & system, then installing magisk again. Now I get the same as your screenshot, but the "rooted but no root permission" result.
Do you know how to fix that?

Aside from trying Magisk 13, that's where I ended up getting stuck, so I think that's just how things are with Magisk 12/10.3.

lukanite said:
Aside from trying Magisk 13, that's where I ended up getting stuck, so I think that's just how things are with Magisk 12/10.3.
Click to expand...
Click to collapse
Oh, ok, thanks. I'll try 13 I guess

Unfortunately it seems like 13 has similar behaviour .. it doesn't complain, but I don't seem to have root access, and on top of that the app crashes here and there. :/ I guess I may have to forego android pay for a little while.

Pre-rooted ROM for XT1644?

Just updated xt1644 to June 2017 update+TWRP+ElementalX kernel. Having problem booting to system after Magisk v14 flash. Rolled back system and uninstalled all Magisk.
With no NFC and no future OTAs coming, I'm ready to try a pre-rooted ROM. Prefer one that is compatible with ElementalX but I can roll back to stock kernel. Also prefer support for E911 USA dialing. Any help appreciated.

Before looking into custom ROMs, have you tried rooting with magisk 13.3? It's still available here at the bottom of the opening post https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
The custom ROMs I've tested (Lineage, Invicta, RR) are compatible with ElementalX and others should be, a quick search of their support thread for ElementalX will reveal if others have tried it before.

echo92 said:
Before looking into custom ROMs, have you tried rooting with magisk 13.3? It's still available here at the bottom of the opening post https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
OK, before completely giving up I'm going to try Magisk v13.3, which worked before. Thanks.
EDIT: Flashing Magisk v13.3 worked without a hitch. I installed Magisk Manager 5.1.1 as before. My only issue is that Magisk Manager keeps prompting me to install v14.0 after any option I select, even after rejecting the install option. There's also a status notification reminder. But I'm nervous about installing v14.0. Would it be advisable to to a Nandroid backup and then let Magisk Manager install v14.0? In any case, thanks for saving the day again echo92.
EDIT2: Tried installing Magisk v14.0 via Magisk Manage 5.1.1. Everything went well but again, the phone froze during the system reboot, just as before. Rolled back to Magisk 13.3 Nandroid backup and my system is working fine again without the latest Magisk update.

mel2000 said:
OK, before completely giving up I'm going to try Magisk v13.3, which worked before. Thanks.
EDIT: Flashing Magisk v13.3 worked without a hitch. I installed Magisk Manager 5.1.1 as before. My only issue is that Magisk Manager keeps prompting me to install v14.0 after any option I select, even after rejecting the install option. There's also a status notification reminder. But I'm nervous about installing v14.0. Would it be advisable to to a Nandroid backup and then let Magisk Manager install v14.0? In any case, thanks for saving the day again echo92.
EDIT2: Tried installing Magisk v14.0 via Magisk Manage 5.1.1. Everything went well but again, the phone froze during the system reboot, just as before. Rolled back to Magisk 13.3 Nandroid backup and my system is working fine again without the latest Magisk update.
Click to expand...
Click to collapse
JX Nougat 8/17 modified stock ROM is fast, prerooted, and has 6/17 security update (used to be called CreamPie ROM)

HueyT said:
JX Nougat 8/17 modified stock ROM is fast, prerooted, and has 6/17 security update (used to be called CreamPie ROM)
Click to expand...
Click to collapse
Thanks HueyT, that looks like a good backup prospect. In the meantime I'll be doing some research on that ROM to see how well it fits.

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

Anyone had any luck with newer versions of Magisk on MK2000 (or similar) kernel?

In order to be able to run Charter Spectrum, (and other television streaming applications) I've been looking to use some of the more sophisticated root-hiding technologies made available by newer versions of Magisk. I'm currently on version 23 of Magisk itself, and 24.1 of the app, but afraid to go any higher with either due to reports of non-boot conditions or incompatibility with newer versions of the Magisk app itself.
Has anyone been brave enough to try current versions of Magisk with Alpha/Omega Rom and MK2000 kernel (or other comparable custom kernels)? If so, did you have a similar problems, (no-boot, Magisk app ceasing to function, etc.) did it work perfectly, or was there some other outcome?
Your input is very much welcomed!

Bill720 said:
In order to be able to run Charter Spectrum, (and other television streaming applications) I've been looking to use some of the more sophisticated root-hiding technologies made available by newer versions of Magisk. I'm currently on version 23 of Magisk itself, and 24.1 of the app, but afraid to go any higher with either due to reports of non-boot conditions or incompatibility with newer versions of the Magisk app itself.
Has anyone been brave enough to try current versions of Magisk with Alpha/Omega Rom and MK2000 kernel (or other comparable custom kernels)? If so, did you have a similar problems, (no-boot, Magisk app ceasing to function, etc.) did it work perfectly, or was there some other outcome?
Your input is very much welcomed!
Click to expand...
Click to collapse
Hello, your on the latest version that works with Oreo 8.0 at this time. Magisk 25.2 does not work. When I installed Magisk 25.2 app, it would not open. So I just uninstalled the Magisk app and reinstalled a lower version and that fixed it. I am also running Stock Oreo 8.0 ezV2020 kernel.

Darnrain1 said:
Hello, your on the latest version that works with Oreo 8.0 at this time. Magisk 25.2 does not work. When I installed Magisk 25.2 app, it would not open. So I just uninstalled the Magisk app and reinstalled a lower version and that fixed it. I am also running Stock Oreo 8.0 ezV2020 kernel.
Click to expand...
Click to collapse
Thanks for the datapoint. Can a newer version of Magisk itself be used with version 24.1 of the app?

Bill720 said:
Thanks for the datapoint. Can a newer version of Magisk itself be used with version 24.1 of the app?
Click to expand...
Click to collapse
I was mistaken, version Magisk-v24.3.apk is the latest version that will work with the Lgv20 Stock Oreo. And Magisk 24.3 would be the latest version. Just install the apk file from GitHub. Do direct install. I just updated my Lgv20 and it works.

Darnrain1 said:
I was mistaken, version Magisk-v24.3.apk is the latest version that will work with the Lgv20 Stock Oreo. And Magisk 24.3 would be the latest version. Just install the apk file from GitHub. Do direct install. I just updated my Lgv20 and it works.
Click to expand...
Click to collapse
Indeed. The version 24.3 apk installed beautifully, and version 24.3 of Magisk did the trick as well. Unfortunately, after enabling Zygisk and restarting, the device now hangs indefinitely on the boot animation .

Bill720 said:
Indeed. The version 24.3 apk installed beautifully, and version 24.3 of Magisk did the trick as well. Unfortunately, after enabling Zygisk and restarting, the device now hangs indefinitely on the boot animation .
Click to expand...
Click to collapse
I never enabled Zygisk, Do you have a backup of your boot image in twrp? I would re flash the boot image. Or you can try to boot into twrp and run Magisk-uninstaller-20210117.zip Then install the Magisk apk again to get Magisk installed.

Darnrain1 said:
I never enabled Zygisk, Do you have a backup of your boot image in twrp? I would re flash the boot image. Or you can try to boot into twrp and run Magisk-uninstaller-20210117.zip Then install the Magisk apk again to get Magisk installed.
Click to expand...
Click to collapse
I followed a bunch of rabbit trails on this one. Tried disabling Xposed Framework because someone said that it might interfere with Zygisk. No change. Tried disabling all of the Magisk modules, but it still hung. Finally, I did the rename-magisk-apk-file-to-uninstaller.zip trick and uninstalled it through TWRP. The device still hangs on boot. I'm thoroughly regretting this experience right about now. The V20 might just be toast.
Update: it did boot up eventually after uninstalling Magisk completely. I'll have to revisit this later in the day.

Phew! It's back in service. Enabling Zygisk is definitely the thing that causes it to incompletely boot, however.
Update: And it's gone again. I tried enabling Zygisk a second time, but now, I cannot uninstall Magisk from within TWRP any longer because it can't mount /data. It can't mount data because device encryption is enabled. I tried using the "locksettings clear --old xxxx" adb shell command, but it is not accepted:
java.lang.NullPointerException: Attempt to invoke interface method 'android.os.IBinder com.android.internal.widget.ILockSettings.asBinder()' on a null object reference
at com.android.commands.locksettings.LockSettingsCmd.onRun(LockSettingsCmd.java:62)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:54)
at com.android.commands.locksettings.LockSettingsCmd.main(LockSettingsCmd.java:50)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:284)
Click to expand...
Click to collapse
Any ideas here, anybody, or am I totally screwed?

Bill720 said:
Phew! It's back in service. Enabling Zygisk is definitely the thing that causes it to incompletely boot, however.
Update: And it's gone again. I tried enabling Zygisk a second time, but now, I cannot uninstall Magisk from within TWRP any longer because it can't mount /data. It can't mount data because device encryption is enabled. I tried using the "locksettings clear --old xxxx" adb shell command, but it is not accepted:
Any ideas here, anybody, or am I totally screwed?
Click to expand...
Click to collapse
That's so odd because I enabled Zygisk on my phone and it booted but I did not have xposed installed. If the data partition is encrypted the only way I know of getting rid of that is to do a format in twrp. That will erase everything on the phone. I don't have any ideas maybe some one will chime in.