Magisk General Support / Discussion

Search This thread

XenonF-Dev

Member
Apr 28, 2021
9
11
MagiskHide on for SafetyNet - yes
Hidden / renamed Manager - not necessarily
Indeed, I was thinking on what I had done back in the day, since I try to be as safe as possible in these things, my bad for not saying it 😅.


Easiest / least fraught way to recover device:

If you did 'nandroid' backup (Twrp backup) of partitions before you rooted, simply do TWRP Restore of boot partition. (If you ever tried Direct Install with Recovery mode selected -should NOT be used on your device - you may need to restore recovery also, or just reflash TWRP.)

If not:
Get ADB working on a PC
Download full ROM package from OEM.
Extract boot.img
flash from PC using 'fastboot flash boot boot.img' ADB command.

I have checked the phone and both PCs in which I know I did the rooting steps looking for any kind of backups, without avail. Only OEM version I found is 31.02, and then the subsecuent updates for the firmware, which only contains boot.img.p.
I'm not sure if I should try to just use the stock 31.02 boot.img, since I can't remember which firmware version I had before the bootloop (Yeah, I will never do this kind of stuff without writting everything down, learned it the hard way ...)
tusch00101 backups from the upgrading progress are sadly offline too. Would be safe to use the stock (31.02) boot.img with twrp recovery?

To re-root, ensure you have uninstalled ANY Magisk Manager or App (especially renamed instances). See release notes re changed hiding methods / incompatibly:
https://topjohnwu.github.io/Magisk/releases/22000.html

Try re-rooting with latest Magisk App. Recommend Patching Image method, but can rename apk to zip to flash from custom recovery.

In the (likely at present) event of issues with your device, re-flash UNPATCHED boot.img, download older (working) Magisk zip installer, and flash from TWRP. If Manager is not installed in that process, install the corresponding Manager for that build, not newer App.

Also, be sure to read official Installation Instruction page:
https://topjohnwu.github.io/Magisk/install.html 🤠 PW
I still have the Magisk manager and Magisk .zip versions I used a year ago as last resort, although I would like to know if using current Magisk.apk renamed to Uninstall.zip on TWRP could help on fixing the bootloop in case the boot.img I have is risky to use, and if doing so what I would loose or have to be wary off (Deleted folders, OS overwriting recovery partition, etc) to prepare ahead.

Thanks again for everything, I'm starting to see the light after the tunnel 🙂
 
  • Like
Reactions: ipdev

pndwal

Senior Member
Jun 23, 2016
2,199
1,399
Sydney
Xiaomi Redmi Note 7
Thanks for the info, I was on that page throughout Saturday though. Weird that unofficial LOS doesn't let you boot without Gapps,
I think this may be fairly unique to builds for this device, and maintainer doesn't know why either:
https://forum.xda-developers.com/t/...al-mi-pad-4-plus-clover.4178757/post-84664747
isn't the point of LOS to let you use the OS without Google? lol
I think LOS's purpose was to pick up from where CM left off after a falling out among the team led to that project's abandonment...

The point of CM was certainly not to be free of Google Proprietary Apps however. In fact it bundled these in ROM until Google hit Steve Kondik (Cyanogenmod) with a cease-and-desist order for including these.

He thought (and posted) that CM was dead and almost ditched the project, but Google seemed to realise they were SHOOTING THEMSELVES IN THE FOOT and clarified that they would still allow GApps to be sideloaded by end custom ROM users (but not packaged with custom ROMs) in short order.

Steve breathed a sigh of relief and got on with the job, Google shut their mouths, and others got OpenGapps.org established to make sideloading GApps simple for custom users, and those users were elated that they could still have their cake and eat it too... 😁

In fairness to Google, since that debacle, they have made a number of concessions to custom AOSP devs and users.

For example, while fighting unscrupulous OEMs and resellers who have tried to bundle Google's proprietary apps with uncertified devices (Chinese etc), and later, provided guides for sideloading the same, they have established a white list expressly to allow GApps to be run on these same devices as long as a Custom ROM is installed (although it seems to work also for stock 😉) by registering device by submitting Google Services Framework Android ID. (Without this, GApps can often be set up, but users are prevented from registering a Google account to use them).
https://www.google.com/android/uncertified/

Need for this, CDD & CTS and companies ignoring these are discussed here, and alternatives to GApps (still use minimal Google services) are touched on at the end of the article:
https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/

Nb. While such whitelisting is not generally needed for custom ROM or Magisk users employing spoofing techniques (certified fingerprint, etc), I'm guessing that this whitelist will likely be essential for many users wishing to to use GApps after final/full Hardware Keystore Attestation rollout.

At that time, SafetyNet pass as well as the use of a number of security centric apps will in all probability be impossible, and users whose Google Services Framework Android ID doesn't indicate a certified device (devices supplied with China stock ROMs especially) will suddenly need to register to use GApps at all. At least, that's my educated guess! 😬
Anyway I'm sticking to MindtheGapps even if it's too bloaty for my liking. Seems like this package is best for LOS.
Perhaps, but I think mileage may vary considerably between various ROMs and devices.
Fingers crossed that with the next LOS nightly this method continues working and doesn't throw some weird errors at me...
All best to you!
I miss the old days of Android when we didn't have to deal with Safetynet or A/B partitions
Don't we all... But that's the cost of progress!

"Everything's gonna run on a paying basis.
Out with the spiritual mumbo-jumbo and the backward ways.
We're gonna see a brave new world where they hook us all up to a grid.
Yes, a veritable age of reason.
Like the one they had in France. Not a moment too soon.
Not a moment too soon."
O Brother Where Art Thou

😜 PW
 
Last edited:

pndwal

Senior Member
Jun 23, 2016
2,199
1,399
Sydney
Xiaomi Redmi Note 7
Hi all! Thank you John Wu for this support/discussion thread. I'm sure it's helped many folks.

I was wondering if there exists a version of TWRP for Android 10 devices, specifically the H96 Max TV box (specs are here: https://www.amazon.ca/Android-LONGY...=1&keywords=H96+Max+2gb&qid=1620071209&sr=8-6).

Here's a bit of context: while in the recovery interface (the built-in one, not TWRP), I tried rooting the device by applying an update from sd card using the latest Magisk version (in .zip format) but it gave me an error saying signature verification failed. I figured it is because recovering with TWRP is preferred, but it seems like TWRP does not support my device ... Any ideas of workarounds/alternative solutions ?

Cheers :)
Very much doubt you'll have TWRP for that; these are device specific, and would need to be compiled from released source code...

However, that is not needed apparently.

W/ Android 10, you have special 'loader' in Developer options, and this is reported to work to flash image files. Guess you could extract / patch boot.img yourself and flash, but one is provided (with method) here:
https://forum.xda-developers.com/t/h96-max-rk3318-android-9-0-rooted-with-su.3965598/post-84029309 All best! 😋 PW
 
  • Like
Reactions: ipdev and J.Michael

pndwal

Senior Member
Jun 23, 2016
2,199
1,399
Sydney
Xiaomi Redmi Note 7
Would be safe to use the stock (31.02) boot.img with twrp recovery?
Depends what you mean by safe! You can generally recover by flashing back a previously working boot.img in case of problems.

Really, you need to ensure boot.img matches current ROM. That's why you unroot (restore images), upgrade, patch LATER boot.img, then flash that to re-root.

You mentioned "subsecuent updates for the firmware, which only contains boot.img.p." Do you mean OTA update?

This seems to indicate that boot.img has been updated from 31.02. You should be able to determine current ROM from Settings, About device.

If it is later, and you can't find a complete ROM package (Nb. You may be able to extract from OTA update, but if it's a space-saving incremental update this may not be possible as it may simply be binary-patch for existing images on your device), after Update and before to rooting, you could make a TWRP backup incl. boot.img, rename resulting boot.emmc.win file to boot.img and try patching / flashing that. No guarantees, but usually works. PW
 

pndwal

Senior Member
Jun 23, 2016
2,199
1,399
Sydney
Xiaomi Redmi Note 7
Sorry if this has been answered. I did search but it wouldn't stay in this thread.
In Search, click settings cog, click Everywhere, change to This Thread. 👍
On Pixel 5, I've been completely uninstalling Magisk before the monthly update. I'm on 22.1 stable. When I press "uninstall Magisk", I get the dialog to "restore images" or "complete uninstall". I've always chosen complete uninstall but now that does nothing, even on reboot, and even after uninstalling all modules.

Should I now be choosing restore images instead? When was this changed?
Haha, yes!

It's all that is needed for updating, and means all Magisk Settings, modules etc will remain (in /data/adb) and save setting up again when Magisk is restored... These survive Magisk Uninstall this way, as well as App Uninstall...

However, it does seem Complete Uninstall is actually broken ATM at least for some, while Restore Images apparently still works:
zputnyq commented 24 days ago

Update: even on 22102, it's still the same.

NB: No problem with restore image only complete uninstall that doesn't work.
https://github.com/topjohnwu/Magisk/issues/4140

Hope it's fixed soon! 😏 PW
 

pndwal

Senior Member
Jun 23, 2016
2,199
1,399
Sydney
Xiaomi Redmi Note 7
Are you sure? In the installation guide it explicitly says you need the recovery.img if there is no ramdisk.
Yes, Installation Instruction page may actually be misleading and could use some clarification, but John does actually cover this in a document linked from that page.

Click link for "(P.S.2 If you are interested in how Android boots and how it affects Magisk, check out this document)" at the end of the Getting Started section. The last paragraph in the linked Android Booting Shenanigans doc mentions that Type III devices including Xiaomi models may still accept initramfs (ramdisk) in boot.img.

And here's a (pull) request for clarity on this:
https://github.com/topjohnwu/Magisk/pull/4130 🤠 PW
 
Last edited:

sereksim

Member
Dec 11, 2020
8
1
Of course I am 100% sure, I have Mi 9T
Yes, Installation Instruction page may actually be misleading
Okay ,thx

So, just to be clear: I download the zip-file from xiaomi.eu, extract boot.img, choose Magisk -> Install -> *not* Recovery Mode -> Select and Patch File -> Let's Go, boot to fastboot/twrp and flash the modified boot.img, right?

Is it necessary/recommended to uninstall the old Magisk version manually first, or is it okay to just install the new one?
 

zgfg

Senior Member
Oct 10, 2016
5,109
2,414
Okay ,thx

So, just to be clear: I download the zip-file from xiaomi.eu, extract boot.img, choose Magisk -> Install -> *not* Recovery Mode -> Select and Patch File -> Let's Go, boot to fastboot/twrp and flash the modified boot.img, right?

Is it necessary/recommended to uninstall the old Magisk version manually first, or is it okay to just install the new one?
If the old Magisk Manager (or Magisk apk - depending what was your previous version) was hidden, then you may have problems that Magisk apk will not recognize that Magisk was installed (once you patch and flash).
Some have the same problem even without hiding Magisk Mngr/apk - in that case, find Magisk mngr/apk (or renamed) in Settings/Apk and uninstall

I hope you didn't try to patch/flash Recovery - in that case restore your TWRP (I don't know where to find original recoveey for Xiaomi.eu, but you need TWRP anyway)

Otherwise - I don't see how could you have Magisk installed if you didn't patch/flash boot img yet, and while (first time) switching to Xiaomi.eu you had to Format Data, hence you could not have the old Magisk db on Data either
 
  • Like
Reactions: J.Michael

Uluru25

Senior Member
Nov 27, 2016
76
14
Samsung Galaxy A6
Redmi Note 8
Okay ,thx

So, just to be clear: I download the zip-file from xiaomi.eu, extract boot.img, choose Magisk -> Install -> *not* Recovery Mode -> Select and Patch File -> Let's Go, boot to fastboot/twrp and flash the modified boot.img, right?

Is it necessary/recommended to uninstall the old Magisk version manually first, or is it okay to just install the new one?
I don't know if your phone behaves different to mine (Redmi Note 8T) in this regard, but since it was delivered initially with Android 9 and since I was able that time to flash magisk as a zip-file from the TWRP recovery I also tried this for magisk v22.1 (renaming the. apk file to. zip) and it worked perfectly.
 

sereksim

Member
Dec 11, 2020
8
1
Okay so I patched the boot.img with Magisk, and restarted into fastboot-mode, but flashing the new image didn't work:
1620128978539.png

Any suggestions?😬
 

sereksim

Member
Dec 11, 2020
8
1
I don't know if your phone behaves different to mine (Redmi Note 8T) in this regard, but since it was delivered initially with Android 9 and since I was able that time to flash magisk as a zip-file from the TWRP recovery I also tried this for magisk v22.1 (renaming the. apk file to. zip) and it worked perfectly.
Okay, maybe I will try that, if the recommended way doesn't work...
 

zgfg

Senior Member
Oct 10, 2016
5,109
2,414
Okay so I patched the boot.img with Magisk, and restarted into fastboot-mode, but flashing the new image didn't work:
View attachment 5299255
Any suggestions?😬
It says 0 KB, but then the file too big - how big is really your original boot.img and the patched one (mine is cca 21 KB)?

When calling fastboot without the path for the file, file must be in the ADB directory, is it?
Are you able to flash the same way the original boot.img or twrp.img?

Btw, you should have TWRP, why don't you Install the patched img from TWRP (select img files - by default it shows only zip files) and select Boot as the target partition

I assume Magisk did not report an error when you were patching, and that you have not only Bootloader unlocked (you have to, since you switched to Xiaomi.eu) but also that upon installing Xiaomi.eu you re-enabled OEM Unlocking in Developer menu (otherwise it blocks flashing)

And test with fastboot devices before you attempt to flash from fastboot
 

XenonF-Dev

Member
Apr 28, 2021
9
11
Thanks again for all the helpul info, still I'm not 100% sure how to proceed, which will be probably because I haven't exposed everything clearly (or I could be missing something 😅), so I will try my best now.
Depends what you mean by safe! You can generally recover by flashing back a previously working boot.img in case of problems.
For me safe means keeping the installed apps data as intact as possible, that is, recovering from the bootloop and beign able to reroot (ideally) again without loosing installed apps data (I also don't remember the credentials for the phone G Account, but that is discardable in the worst case scenario).
This seems to indicate that boot.img has been updated from 31.02. You should be able to determine current ROM from Settings, About device.
I checked Settings option on TWRP, but haven't seen the about device option sadly (using TWRP 3.0.2-0-decker-2, if that helps). Right now I'm only able to access recovery on the phone.
You mentioned "subsecuent updates for the firmware, which only contains boot.img.p." Do you mean OTA update?

This seems to indicate that boot.img has been updated from 31.02. You should be able to determine current ROM from Settings, About device.

If it is later, and you can't find a complete ROM package (Nb. You may be able to extract from OTA update, but if it's a space-saving incremental update this may not be possible as it may simply be binary-patch for existing images on your device), after Update and before to rooting, you could make a TWRP backup incl. boot.img, rename resulting boot.emmc.win file to boot.img and try patching / flashing that. No guarantees, but usually works. PW
Yeah, they are small .zip files which were bundled on the S60 Rooting topic package, so I guess they are binary-patches. I guess I could try to make a NANDroid boot's backup and then try the uninstall.zip method with the magisk version I used, and if that fails try to use 31.02 boot.img and try to be lucky and in case something goes bad, I could restore the NANDroid bootlooping backup.
 

Xellerate

Member
Apr 8, 2020
9
2
how do you flash magisk with heimdall, the installation only explains how to install magisk with odin, ive tried to flash with heimdall, everything worked apart from the touchscreen, so i coundlnt even get out of the set up screen
 

Xellerate

Member
Apr 8, 2020
9
2
how do i flash magisk with heimdall, what i did was that i pathed the ap with the magisk app, then moved it to pc then extracted to flash the files seperatley since you cant flash the ap itself and it booted up without touchscreen
 

digger16309

Senior Member
Jul 17, 2014
367
108
OnePlus 5
Google Pixel 5
Haha, yes!

It's all that is needed for updating, and means all Magisk Settings, modules etc will remain (in /data/adb) and save setting up again when Magisk is restored... These survive Magisk Uninstall this way, as well as App Uninstall...
Restore Images doesn't work for me. I get a message that says:

stock backup does not exist!

I have the stock boot.img from April - where do I need to place the file so Magisk will find it?

--------------------

Nevermind - that's what I did - I patched the stock boot.img file again then restored back to it.
 
Last edited:

J.Michael

Senior Member
Jan 20, 2018
598
366
how do i flash magisk with heimdall, what i did was that i pathed the ap with the magisk app, then moved it to pc then extracted to flash the files seperatley since you cant flash the ap itself and it booted up without touchscreen
After it booted up without touchscreen, have you tried flashing unpatched stock files with Heimdall? Are you then back where you started, no Magisk but touchscreen works?

If so, I would say that shows you are using Heimdall correctly.

If you are using Heimdall, I would assume you are have a Samsung device. Have you read the Imstallation Notes sections about Samsung? I would expect you to have to install Magisk to recovery. There is some disagreement over whether you need to check the Recovery option in Magisk Manager before patching the AP.tar file, or whether Magisk Manager will always install to recovery when presented with an AP.tar file.
 
  • Like
Reactions: pndwal

J.Michael

Senior Member
Jan 20, 2018
598
366
Thanks again for all the helpul info, still I'm not 100% sure how to proceed, which will be probably because I haven't exposed everything clearly (or I could be missing something 😅), so I will try my best now.

For me safe means keeping the installed apps data as intact as possible, that is, recovering from the bootloop and beign able to reroot (ideally) again without loosing installed apps data (I also don't remember the credentials for the phone G Account, but that is discardable in the worst case scenario).

I checked Settings option on TWRP, but haven't seen the about device option sadly (using TWRP 3.0.2-0-decker-2, if that helps). Right now I'm only able to access recovery on the phone.

Yeah, they are small .zip files which were bundled on the S60 Rooting topic package, so I guess they are binary-patches. I guess I could try to make a NANDroid boot's backup and then try the uninstall.zip method with the magisk version I used, and if that fails try to use 31.02 boot.img and try to be lucky and in case something goes bad, I could restore the NANDroid bootlooping backup.
@pndwal knows what you mean by "safe".
Noone can guarantee safe.
I think it is a very bad idea to keep going with the phone attached to a Google account you can not log into.

There is a warning to disconnect from any Google account before running Odin. You may not have a Samsung phone, you may not be using Odin, but I think the potential for interference from Google still exists.
 

XenonF-Dev

Member
Apr 28, 2021
9
11
@pndwal knows what you mean by "safe".
Noone can guarantee safe.
I think it is a very bad idea to keep going with the phone attached to a Google account you can not log into.

There is a warning to disconnect from any Google account before running Odin. You may not have a Samsung phone, you may not be using Odin, but I think the potential for interference from Google still exists.
My bad, didn't get it 😅.Well, I tried starting with safemode using the method described on tusch00101's blog post about this phone, but I wasn't lucky :cry:.
So, what path should I take then? Most apps I want to keep info are from F-Droid repository and I could make a manual backup of those files in case sh*t hits the fan.

Edit: After getting a 64GB sd for making a backup, I saw that TWRP named the backup "LTE_D0201121.0_S60_0.038.00" so I guess I'm in the last revision that was discussed on the S60 root topic. Sadly, I can't find any sources for the so called update38, nor I think it is available as a full OTA update and probably only binary-patch version. The good side is that at least I got more info :). Yet again, thanks for everything so far and in advance.
 
Last edited:

OP6Tuser

Member
May 4, 2021
6
0
I just got a factory reset oneplus 6T. I heard that the newest version of twrp (3.5+) and magisk (v22+) dont work together and that wifi doesnt work if you use them both. Is this true? What versions of twrp and magisk work well together for OP6T?
 

Top Liked Posts

  • 1
    Full stock rom of a.61 is not available on the internet rn.
    Also there is no twrp for realme c3 atm iirc. So I can't flash any zips.
    1
    Full stock rom of a.61 is not available on the internet rn.
    Also there is no twrp for realme c3 atm iirc. So I can't flash any zips.
    Hi.
    I am not familiar with Realme.

    I did a quick check and see there is TWRP build over in the Realme C3 forums.
    [RECOVERY][TWRP][RMX2020] TWRP 3.5.2 [UNOFFICIAL] - xdaThread - Link
    Looks like it has only been out for a month and I am the only one who hit the like button so far. ;)

    Quite a few custom rom threads but, I did not see a thread for Stock rom / firmware.
    Realme C3 - xdaForum - Link

    Hope this is the correct TWRP for your device.
    Cheers. :cowboy:

    Edit:
    @SaikiK
    I see, you device might have rollback protection.
    To be safe, you might want to ask in the C3 TWRP thread before you try it.
    1
    I use Termux. Sometimes I need a root shell, so I granted root permanently to Termux, so I can use 'sudo bash' in Termux. But, as there is no password prompt, this is actually a security flaw. So I wanted to revoke root access and grant root access only on demand, when I really need it.

    Revocation succeeded, but I can only grant root access permanently and not temporarily. The latter only happens when I grant root access to an app for the very first time.
    Can't reproduce. If I revoke superuser access for Termux and then run su I can pick "forever", "once" or one of the set time periods.
    1
    Where is the canary build?
    The latest Canary apk is always linked in the main Magisk GitHub repo:
    https://github.com/topjohnwu/Magisk
  • 11
    Latest Debug (Canary)
    Changelog and Release Notes
    https://github.com/topjohnwu/magisk-files/blob/ea57c9b33b3a6ce2e0e65ce4c33dfb1c01552fcb/notes.md :

    Magisk (f49966d8) (22103)​

    • [App] Update snet extension. This fixes SafetyNet API errors.
    • [App] Fix a bug in the stub app that causes APK installation to fail
    • [General] Fix a C++ bug that causes undefined behavior
    • [MagiskHide] Update package and process name validation logic

    Diffs to v22.1​

    • [General] Remove all pre Android 5.0 support
    • [MagiskPolicy] Remove unnecessary sepolicy rules
    • [App] Update snet extension. This fixes SafetyNet API errors.
    • [App] Fix a bug in the stub app that causes APK installation to fail
    • [General] Fix a C++ bug that causes undefined behavior
    • [MagiskHide] Update package and process name validation logic
    👍 ...And things are all Rosy 'n Safe in the Custom Mod. world once again... but ironically, only on the bleeding edge... (Confirmed on my RN8T. 🙂 )

    News for those not wanting to get cut (Public Stable / Beta users) below. 😜

    Thanks John... And other collaborators for additional fixes! PW
    9
    Latest Debug (Canary)
    Changelog and Release Notes
    https://github.com/topjohnwu/magisk-files/blob/56d4ca44e12927217ae761df0874e3cd7d05cea4/notes.md :

    Magisk (fb8000b5) (22104)​

    • [App] Hide annoying errors in logs when hidden as stub
    • [App] Update stub implementation
    • [App] Some internal code refactoring
    • [App] Update snet extension implementation

    Diffs to v22.1​

    • [App] Update snet extension. This fixes SafetyNet API errors.
    • [App] Fix a bug in the stub app that causes APK installation to fail
    • [App] Hide annoying errors in logs when hidden as stub
    • [General] Remove all pre Android 5.0 support
    • [MagiskPolicy] Remove unnecessary sepolicy rules
    • [General] Fix a C++ bug that causes undefined behavior
    • [MagiskHide] Update package and process name validation logic

    May fix sundry issues with Magisk App! 👍 PW
    9
    Update snet.jar extension
    The existing API key was revoked for some reason.
    Release an updated extension jar with a new API key.

    In addition, add some offline signature verification and change how
    results are parsed to workaround some dumbass Xposed module "faking"
    success results, since many users really don't know better.

    @topjohnwu

    topjohnwu committed 19 minutes ago
    8
    Which logs are helpful when devices bootloops on splash screen?

    I read https://www.didgeridoohan.com/magisk/MagiskHelp but is last_kmsg need be taken after booting to Android after flashing stock boot.img?

    I have took and posted logs by booting to TWRP. Is that a correct way?


    Thanks
    The kmsg (Kernel Message) file is constantly written to while booted into an Android environment.
    System or Recovery.

    A new kmsg file is created every time you boot the device into an Android environment.
    The previous kmsg file is moved to last_kmsg

    Both files are replaced each time you (re)boot into an Android environment.

    Example.

    You boot into system and get stuck at the splash screen.
    Your device is currently writing to /proc/kmsg

    You force a reboot into recovery.
    The previous /proc/kmsg was moved to /proc/last_kmsg
    Your device is currently writing to /proc/kmsg

    /proc/kmsg is now the current recovery boot
    Your previous boot into system is now /proc/last_kmsg

    If you now reboot from recovery into recovery again.
    The previous /proc/kmsg is moved to /proc/last_kmsg
    Your device is currently writing to /proc/kmsg file.​

    /proc/kmsg is now the current recovery boot
    Your previous boot into recovery is now /proc/last_kmsg


    Note:
    • Newer devices use /sys/fs/pstore instead of /proc/last_kmsg
    • You normally need heightened privileges (root) to grab kmsg or pstore.
      A custom recovery normally allows you root access.

    Hope it helps more than confuse. 🙃

    Cheers. :cowboy:
    8
    Strange how people think they don't need to read the other posts but expect that their questions should be addressed and answered😌
  • 1047
    This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases.
    All information, including troubleshoot guides and notes, are in the Announcement Thread
    Donate Magisk 1N9fG13ccZFpaPqV167f24Fjpp1R588BVR BTC to mantain it alive.
    155
    Hello, I haven't given much support on XDA lately. It can be resulted from
    • University started and I have limited free time. In fact, I mostly develop during midnight
    • I live in Taiwan, which has large time zone differences between my European/American contributors/testers, which usually forces me to stay up late at night to discuss/test stuffs.
    • The new version is about to come, I don't want to spend effort on supporting old releases
    The planned update is delayed again and again, to some point I think I'll shed some light about what has been happening lately, also along with some announcements.

    New Forum!
    As you might have already discovered, Magisk got its own subforum on XDA! Many thanks to all the support you gave me, and much more information/features/support is about to come!
    **For developers supporting all the devices that are not using standard Android boot format, feel free to create threads in this section (actually, PLEASE do so) for your favorite devices after v7 is out. As I currently know, Asus devices require signing the boot image before flashing, and is model dependant; Sony devices seems to use ELF kernel that is unpatchable, or some has two ramdisks (inner + outer), both requires different workarounds; LG bootloader locked devices has to manually "BUMP" the boot image after flashing Magisk..... and there may be lots of other crazy boot image formats that haven't come up to my attention yet.
    It is impossible for me to support all these non-standard boot images, and I hope the community can collaborate to make Magisk running across all the devices. Overall, community collaboration is what XDA about :D

    The Pixel Phone
    Some of you might already know this news, that the next Pixel Phone right around the corner seems like it does not have ramdisk in boot image, which pretty much wrecked Magisk in all ways. However, it pretty much doomed root itself too. Kernel modifications is inevitable IMO, so I'll try to migrate my scripts to C programs that could possibly be included into the kernel itself. Note that I'm not familiar with linux kernel, I'm not even sure if my idea and concept is correct or not. But once the device is available, I think developers will find a way to bypass all the difficulties, and I'll do my best to learn things ;)

    Current Progress
    In the past month, I've spent quite some time learning SELinux, so that I can avoid using SuperSU's sepolicy patches. Thanks to the helps and tips from @phhusson and @Chainfire, I finally have a much clearer understanding of how SELinux works. The Magisk core parts (the scripts, boot image patches, new features, more supports) are actually done some time ago. What is causing all the delays is the Magisk Manager.
    To be completely honest, although I can code in Java without much issues, Magisk Manager is actually my first Android application, I had to reach out for assistance, and fortunately awesome developers like @DVDandroid and @digitalhigh contributed a lot, which makes the current Manager awesome.
    After the repo system and module management is mostly done, I was about to do some adjustments and release, but what we really done is decided to add another feature: auto-unroot with per-app settings. I decided to wait for it to be finished, and then do my adjustments. Due to reasons that'll be mentioned later, this feature will likely not be available for the next release (should come in future updates)

    Safety Net Disaster
    Those who are using Magisk for Safety Net bypass purposes must have known that Google recently updated the detection method of my Systemless Xposed. I still have no idea what Safety Net is detecting, so currently I cannot fix it on my side (also because I'm busy working on the next update). However, suhide developed by @Chainfire is able to hide Xposed and worked fine.
    However, only my Systemless Xposed v86.2, which is based on SuperSU's su.d, is supported using that method. v86.2 and v86.5 (latest, Magisk based) have nearly identical binaries, and the only difference is the path where the binaries are stored.
    I'm still not sure what's the real issue for it not being supported, I just hope it is not done intentionally.

    Conclusion
    Due to the fact that my Safety Net bypass is not 100% perfect now, I do not want to spend any more time waiting for auto-unroot to be polished. What I'm doing now is finishing up all the things I'd like to change in Magisk Manager (it has been a while since I last contributed to Manager, my fellow developers are doing all the heavy job), which might take a little more time, after that, packed with tons of information to be announced in Magisk Section, I'll release the long awaited update.

    Hope this lengthy post gives you the idea of the whole situation, and again thanks for all your support!!
    119
    Ah, some Chainfire bashing, I hope it is not too late for me to exercise additional villainy.

    First, let me make clear I have nothing against @topjohnwu, nor against Magisk. Magisk is an interesting project and it certainly displays @topjohnwu ingenuity and persistence. I don't doubt we will see more interesting things from his hands.

    -------------------------

    What has happened here is not all that dark and complicated, from either end. I returned from holidays, and someone pointed me at Magisk. My first thought: interesting!

    Among other things, the thread lists some issues with SuperSU, which in combination with the phrase The developer also requests users to not bug Chainfire with compatibility requests for SuperSU with Magisk from the portal article, raised my left eyebrow by nigh half an inch. The popular systemless xposed mod is apparently now based on it, and apparently it now no longer works with SuperSU, and apparently I'm not supposed to fix that, nor any of the other found issues. I found that a bit weird. So yes, I have told @topjohnwu that I was a bit surprised he was posting about issues with SuperSU without notifying me about them (I can't fix or help fix issues I'm not aware of, after all).

    He's also spreading a modified version of the SuperSU package, which is not all that uncommon, nor necessarily a problem. I have not looked into what he modified, I only ran a few quick tests on one of my devices, and found some commonly used commands run as root to be broken. I have informed him of this as well.

    It appears the tool of choice for Magisk is phh's Superuser, because of some of the mentioned issues with SuperSU. That's fine by itself, but fixing issues in that superuser by incorporating SuperSU's binaries into it is a somewhat questionable practise. After all, SuperSU is a commercial closed-source package that helps pay for my dinner, and superuser is a direct competitor. I have informed him that I was surprised he did this without asking for permission. I have expressed similar surprise on him spreading a modified version of LiveBoot (which helps pay for a snack now and then).
    @topjohnwu has also stated that Magisk's scripts are largely influenced by mine (I have not checked). Scripts based on mine are used all over the place on XDA, some people have crafted amazing things based on them, I have never made an issue of this (otherwise I would have just made them binaries). But yes, I have also stated to him that I don't think it's very nice to base something on one program, and then using that to (almost exclusively) push something directly competing with that program.

    tl;dr Towards @topjohnwu, I have:
    - expressed surprise he has issues getting Magisk to work with SuperSU, and has chosen not to inform me about those
    - expressed surprise he is using SuperSU binaries in a competing superuser without permission
    - expressed surprise he is posting a modified LiveBoot without permission
    - informed him of issues with the modified SuperSU he has posted
    - let him know I thought it wasn't very nice to be applying my scripts to benefit seemingly exclusively that same competing superuser

    To be crystal clear:
    - I have not asked for an apology
    - I have not asked for Magisk to be abandoned, neither the root hiding nor systemless module parts, and certainly not systemless xposed
    - I have not made an issue of any of this anywhere, until this post
    - I have not even specifically asked for anything to be taken down (though obviously in my opinion the other superuser package mixed with SuperSU's binaries, as well as the LiveBoot package, should go)
    - I have not reported this thread to XDA moderators for copyright violations or otherwise

    While my conversation with @topjohnwu may not win any awards for being friendly (though it may win some for brevity), I think all things considered my response has been rather mild. To be perfectly honest, until the apology post, I thought this was over with already. I think the apology post was triggered because I haven't replied to his last PM for a while - I was in the zone, it happens.

    To emphasize again, I have nothing against @topjohnwu, Magisk, or systemless xposed, and it is certainly not my goal to see any of them go. If it can be made to work together with SuperSU, great.

    I get it though: you think of something, you want to see if you can make it work, you finally get it to work, you publish it, it takes off - enthusiasm gets the better of you. Maybe in the rush some mistakes are made. That doesn't mean you have to just drop it and run. None of my stuff would make it past 0.1 if I stopped at the first big mistake :)

    Aside from said being in the zone coding, I usually regret actually responding to these sort of things the day after, which has made me hesitant to reply. Surprise me.
    76
    Thread temporarily closed so everyone sees this.

    The flood of "SafetyNet isn't working for me either!" posts are not helpful, at all. Please refrain from posting further, it will be looked into. Please do not forget that not passing SafetyNet is 100% NORMAL AND INTENDED when you have an unlocked booloader or running custom firmware. These are workarounds and they will be worked around in turn.

    The Flash
    Forum Moderator

    EDIT: Thread is reopened... I will be cleaning any SafetyNet posts for a while to keep the thread clean for real issues.
    74
    Hello everyone!

    I am aware that Google has updated Safety Net that makes Magisk itself a no go for Android Pay. In fact, I witnessed the change live while I am developing the new magiskhide, which should hide all Magisk modules and Magisk installed root.

    Google is serious about Safety Net now, clearly hunting down all possibility to run Xposed with Safety Net passed. I spend quite some time examining the new security measures last midnight, and fortunately it seems that it is possible to run Magisk and root along with Safety Net if no Xposed is running. I'm glad I removed the old root toggle at the right time lol, that is no longer feasible with the latest detection.

    So stay tuned for the next update, it will come with bug fixes, along with the new magiskhide to bypass that Safety Net.

    Google, how will a few systemless mods do any harm :p:p
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone