yashsingh1/xdaforums huggingface dataset:
[Magisk] Drahy:
These are just speculations... and even if this is true we must find a way to "work-around" this somehow... People did miracles already with the root-hiding I believe with the smart people here there is always a way :)
[Magisk] pndwal:
Of course... Just saying... ('Cos I'm in the mood for repeating the same things over and over)... PW
[Magisk] m0han:
I'd rather not be going down that road....
[Magisk] pndwal:
Don't blame you...

Seems Xiaomi don't want untold users to do this either or they wouldn't have provided the facility for a user fix for many devices... Still seems a responsible move to me; when something similar happens (ie Widevine keys are revoked) with several other OEMs users report they are told there's no way to restore / they're lost forever! 🙁

Anyway, I wasn't encouraging you to go to a service centre... I posted as 1) I understand that since you evidently need new L1 keys/certificate to fix this, at least w/ Xiaomi devices, I doubt that

will benefit you, and 2) to clarify that Stock MIUI is not the only solution (and in fact a MIUI port, eg XiaomiEU custom ROM, may be the only option w/ some devices...

It seems you will need to back up / clean install stock (may be able to ascertain if stock supports certificate generation for your device) or XiaomiEU custom (seems this does support) in order to fix yourself; probably need full wipes to restore your ROM of choice too... 🙂 PW
[Magisk] jellybean 4.1:
there is any way to unistall magisk whit out the app?? i have bootloop fron a module and don't have twrp install
[Magisk] zgfg:
Check GitHub, Documentation, Wiki if you can boot to Android Sage mode to disable Magisk modules
[Magisk] zgfg:
Magisk Delta (but probably not specific to)

Xiaomi, MIUI 13/A12

I just set Second Space on my phone - seems I will need to use for business applications and corporate phone

YASNAC, Play Integrity pass (Device Integrity) - Xiaomi.eu ROM forces Basic attestation and 'hides that BL is unlocked' and Device is certified

S-Check and Oprek fully pass

Ruru and TB-Checker pass but detect Second space

Momo still detects Magisk (?) and BL unlocked

Explanation:

Second space works kind of dual boot. You can switch between the First and Second Space (takes me cca 5 seconds)

All apps must be separately installed to Second space, Google acc too, etc

Second space has also its own Internal storage (empty when you set)

Hence eg, I don't have Magisk app in the Second space and I had to install all the above checkers again to the Second space

PS: Mounts applied by Magisk when device booted still apply (as expected) in Second space:

- Ads are blocked (Systemless hosts)

- My Sytemless debloater

- YouTube Re-Vanced (root)

However, modules like LSPosed are not active in Second space

Not so bad thing
[Magisk] badabing2003:
What device?

Can you get into bootloader mode?
[Magisk] Iridule:
Hello, I am new to Magisk but have rooted my Moto Edge and successfully have bank and game apps working using modules USNF, Shamiko, and MagiskHide props conifg...however I realized I have accidently installed the Canary Debug vesion of magisk 25.2 ((25200) (34) ...How do I change to a stable or beta version of 25.2? Or should I just stay on the Canary version? Any help would be appreciated.
[Magisk] J.Michael:
I'd say keep what you've got.
[Magisk] chichino84:
I just tried to update via OTA the December update but apparently something went wrong:

Uninstalled all modules

Restored boot.img

Uninstalled Magisk (stable 25.2)

Installed the OTA (without rebooting)

Opened Magisk app e unisng the inactive slot OTA-option

Rebooted

and now my device don't boot showing the red corruption alarm screen.

Any help please? (Pixel 6a A13 stock ROM)

EDIT:

Phone booted up, but apparently it's still on November update (in Settings>System>System Update still asking for a reboot).

Re-Installed Magisk 25.2 stable, but the process was like a 1st time installation rather than an update.

What should be my safest moves from here to get December update now? Thx
[Magisk] badabing2003:
Disable Magisk modules

Dirty flash factory image (remove -w if you want to keep data)

Boot to system and confirm everything is working fine.

Patch boot.img and flash

I'd do this to both slots if it was my device.
[Magisk] chichino84:
Thx @badabing2003, worked perfectly!

Wondering where I could possibly screwed up with the direct OTA attempt...
[Magisk] pndwal:
You didn't... I / others have posted this before:

... Clearly with every Update you will now need to restore unpatched images (use in-App Uninstall Magisk, Restore Images option) then take update, either OTA or full ROM, but you'll need to obtain new boot image from full ROM for patching (unless you use a custom recovery etc to obtain boot.img from a backup) in any case like A-only device users always needed to... Next, set up Magisk per instructions for a fresh install...

Unfortunately you have no other option until a fix for Install to inactive slot method (bypass for new partition digest checking) is found... 🙃 PW
[Magisk] Lughnasadh:
On the Pixel 6 and 7 series, this method is really hit or miss. Works for some, doesn't for most.
[Magisk] chichino84:
Got it, thx for clarifying this!
[Magisk] Loustsoul:
I am still learning and I have applied some modules and after turning them off the effects are still present. How do I fix it? (For Example, hide clock on the tool/notification bar used the module then realized I need the clock , but I cannot get it back) Please provide support.
[Magisk] J.Michael:
Track down the author of the module and ask *him* if disabling the module reverses its effect.
[Magisk] pndwal:
... Did you reboot? 😛 PW
[Magisk] Loustsoul:
yes. Lots of times.
[Magisk] Loustsoul:
Thank you.
[Magisk] Loustsoul:
Would it work to delete it?
[Magisk] rodken:
If you decide to delete, ensure that the module has been completely removed under /data/adb/modules.
[Magisk] Loustsoul:
I did that, still no clock....
[Magisk] zgfg:
Always better to uninstall ("Remove") a module from Magisk app than by deleting its folder
[Magisk] Loustsoul:
I did not have "uninstall" I only had remove/restore. That means that it was still in the system. Where is uninstall?
[Magisk] zgfg:
Yes "Remove", Magisk, on the next reboot shall uninstall the module

If a module has uninstall.sh script (to clean-up things), it will be executed by Magisk before deleting the folder

If you just delete the folder, uninstall.sh script (if present for that module) cannot be executed
[Magisk] Loustsoul:
Okay, I did that. But still have no clock.
[Magisk] Lughnasadh:
As suggested above, you should really contact the developer of the mod, especially since we don't even know what mod you are talking about.

It may be a specific bug for that specific mod. For example, this sometimes happens with the Pixel Launcher mod but there is a workaround the developer has posted in their thread.
[Magisk] Loustsoul:
The problem is, I also don't know which one did it...:ROFLMAO::ROFLMAO:
[Magisk] zgfg:
Not familiar with your ROM and module

If a module works sysremlessly, its changes cannot be permanent

But if your phone is older / older Android version, custom ROM, etc, then your System is not read-only and a module (if not working sysremlessly) could have made permanent changes

To revert those permanent changes developer had to include uninstall.sh to clean up, but who knows if it does

Again, not familiar with your phone/ROM and module
[Magisk] J.Michael:
Removing the clock display was just a side-effect? No module has a name with "clock" or "status bar" in it?

You could try reinstalling the ROM. That should put you back at the beginning.

Have you checked the Android settings to see if it was something you could have done yourself, without a module?
[Magisk] Loustsoul:
The module I used had the option to hide the clock in the status bar at the top of the device. I actually selected to hide the clock. I also replaced the google search bar at the bottom with my calendar. When I deleted everything the google search bar went back to normal but the clock stayed gone. I cannot find any settings for it.
[Magisk] J.Michael:
Where does a module have options?

Reinstall your modules until you find the right one. Change the option to hide the clock and see if it reverses itself. At worst you will know which module, and you can try to contact the author.

Or, as I said, start over by reinstalling your ROM and make different choices.
[Magisk] jellybean 4.1:
Mi 11 lite 5g lineage os and yes i can boot in bootloader mode
[Magisk] pndwal:
Did you try adb wait-for-device shell magisk --remove-modules command?

No?... Safe mode booting from powered down state works on my Mi Pad 4 w/ LOS 18.1... there are issues w/ timing for Magisk daemon's Safe Mode key combo detection (which this method relies upon) on Xiaomi devices however, but these can be avoided by adjusting timing... See this for specifics:

Magisk cannot detect key events correctly

Further, I guess no data decryption in LOS recovery is your issue with custom recovery methods... Did you consider fastboot booting TWRP? (Temporary boot)... Should be no need to flash it and twrp.me site recommends this:

https://twrp.me/xiaomi/xiaomimi11lite5g.html

... Nb. This is 3.7.0 and 11 branch builds properly support A12.1 also... decryption / file manager may just work in A13 also if you have this (you didn't say), but you'd need to try to know...

🙃 PW
[Magisk] jellybean 4.1:
I try the code but don't work

I will try to boot twrp and delet the modules by manual
[Magisk] bomie:
Hello.. I have problem to get solve. I was installed magisk.apk then Install root. It's request restart. After that it's not boot into system but stuck in fastboot... What should I do?
[Magisk] pndwal:
Fastboot flashed a patched image?... Flash back unpatched image to restore boot... Please say if you make other changes...

Base commit / beta build looks suspicious or very old... What was the source?... PW
[Magisk] krs360:
Has anyone successfully rooted Pixel 6/6 Pro on the new QPR2? If so, how??

Manually patching the boot.img doesn't seem to work.
[Magisk] 73sydney:
Do you mean you cant patch the boot image and it gives an error whilst trying,

or

you can patch it, but you find you dont have root after flashing the patched boot image

please specify which it is and include any errors or screens that provide any useful info

p.s. i still havent flashed the December drop yet, so that should give you a clue as to my schedule for flashing a beta :)
[Magisk] m_pastuszek:
Same issue on latest Android 13 QPR2 Beta 1 T2B1.221118.006. Don't work with PixelFlasher, manual commands, and different Magisk versions. Previously, worked fine with latest Canary.
[Magisk] zgfg:
I don't have Pixel device but if I recall correctly, it was discussed that for A13 (some devices) vendor_boot.img must be patched and flashed
[Magisk] 73sydney:
Again where is the failure?

In patching the image or the patched image not working?
[Magisk] m_pastuszek:
@73sydney the problem is that the patched image just don't work.

Flashing writes partitions correctly, but Magisk stays without root.

@zgfg flashing pathed boot.img and vendor_boot.img don't work too.
[Magisk] zgfg:
You said that you tried with Pixel Flasher - suggesting you to ask in the corresponding thread that is dedicated to Pixels, here we are users of all vendors (Samsung, Xiaomi, etc)

Also, if you previously did Hide Magisk app, you had to unhide before trying to re-install Magisk.

That's a common case resulting that newly installed Magisk app does cannot recognize root
[Magisk] m_pastuszek:
There's solution! It seems that Google broke something in boot image. Flashing pathed image from Pixel 7 makes it working again. See GitHub issue: https://github.com/topjohnwu/Magisk/issues/6441

Pixel 6 -> Pixel 7 boot image

Pixel 6 Pro -> Pixel 7 Pro boot image
[Magisk] pndwal:
Just catching up, n very interesting solution... 👍

Patching vendor_boot.img shouldn't work for any device...

Two GKI Boot Images for P6 series

Vendor ramdisks were moved out of boot.img when GKI became a thing for Treble compatibility and we got the two boot images, vendor_boot + boot.img, the latter retaining the 'generic' ramdisk which constitutes 'ramdisk' for magiskinit purposes...

Four GKI Boot Images for P7 series

With Pixel 7 (A13 LV), boot images have become four with new GKI boot.img further losing generic ramdisk to init_boot.img (so P7 users must patch that) and boot.img retaining basically the kernel only... Also, vendor_boot.img is further split, losing a vendor_boot multi-ramdisk option, dlkm (dynamically loadable kernel modules for boot-time use) to ramdisk in vendor_kernel_boot.img w/ vendor_boot.img retaining vendor ramdisks...

...So P7 boot.img contains kernel only as discussed above...

Magisk has manually added a basic generic ramdisk where missing in boot.img for some time. (This allows legacy SAR A-only devices w/ a compatible bootloader and no OEM supplied generic ramdisk in boot to use Magisk in boot mode instead of recovery mode.) This functionality was also made compatible with some A13 GKIs for P6 series etc (expanding use to "# Stock A only legacy SAR, or some Android 13 GKIs") along with a needed ramdisk compression format fix (I believe only the compression format fix is generally needed) here:

https://github.com/topjohnwu/Magisk/commit/985249c3d0bccff479f8c1efd5967922ab8d855e

It appears that by the fluke of this fix doing more than simply correcting the compression format, a compatible boot.img lacking ramdisk (eg P7 kernel only) can have a working generic ramdisk manually added successfully by Magisk for use in P6...

That a P7 kernel is even compatible is the real surprise to me however!... 😀

... Seems that that beta update may not even boot... Canyie says user reports updating simply rolls back to old ROM!(?)...

Out of interest, do you need to use disable-verity / --disable-verification in vbmeta to boot using P7 patched boot.img in P6?

👍 PW
[Magisk] Lughnasadh:
The sources are extremely similar.
[Magisk] m_pastuszek:
I didn't need to disable verification. Actually, when I made this operation, system didn't boot. Just showed that system is corrupted. I've needed to reflash factory image again.
[Magisk] topjohnwu:
Cool, so it is detecting something I don't know.

I'll recruit some testers soon. Need to try all kinds of wild experiments.

Keep in mind, Magisk is not aimed for Android Pay, and the discussion of Android pay should be in the Magical phh thread :)

Once I need testers, I'll let all if you know. Right now I need to focus on getting Magisk working on all devices.

Thanks for all the support!
[Magisk] allen099:
Sounds great [MENTION=4470081]topjohnwu[/MENTION]. I posted in that thread as well. Let me know if I can jump onboard and help with anything that's needed. Maybe there's a way to hide that img file, or move it to a different directory, when unmounting root and then move it back after the timer expires.
[Magisk] uoiea0:
Tried to install it on stock unmodified MIUI 6.8.4 china developer ROM (Android 5.1) on Xiaomi Redmi Note 3 Pro. I used TWRP (fastboot boot twrp.img), Magisk v2 installed without any error, MIUI boots successfully but logfile says:

Magisk post-fs mode running...
Magisk post-fs-data mode running...
All mounts failed, nothing to do :(
Magisk late_start service mode running...

Restored backup and tried v3 but it is same as with v2.
[Magisk] gaganit:
Okay to flash v3 directly over v1??
[Magisk] KevinX8:
Having some issues on my LG g3 running stock based rom, upon booting my phones led begins to blink forever (the led usually finishes blinking when boot process is finished) and also my vibration motor no longer works. I know these symptoms are really strange and make no sense but they go away after removing magisk. Other than that everything else seems to work so I am really confused here. I have attached my xposed logs as there seems to be some unusual error, it looks like magisk is unmounting itself too early on boot and my phone begins to panic, this is just a hypothesis though
[Magisk] Compgeek316:
No typo. I installed Xposed 86.3 when I installed Magisk v1. Then updated to Magisk v2 and Phh's Superuser for Magisk v2 but did not update Xposed.
[Magisk] Shockz:
Worked fine for me.
[Magisk] gaganit:
Where is the Magisk Manager app? I update from v1 to v3 and app is gone
[Magisk] Cronus89:
Since v2 it is included in phh's SuperUser install
[Magisk] gaganit:
I installed the superuser v2 but still no manager app
[Magisk] teddy0209:
uninstall the previous one, extract the new apk from the zip, then install...
[Magisk] nextelbuddy:
I flashed V3 on Stock Android N G build, Nexus 6P here. I see the Magisk Manager and open it, I click on Disable Root and nothing happens.

what is supposed to happen?i can toggle Selinux off but as soon as i touch Disable root again it re enables but nothing else happens.

---------- Post added at 11:37 PM ---------- Previous post was at 11:32 PM ----------

never mind its working. I just had to install the V2 superSU app with the playstore link in the post

https://play.google.com/store/apps/details?id=me.phh.superuser

and now its working fine. toggle works as expected.
[Magisk] dancer_69:
I just flashed v3 and for first time Magisk Manager worked like it should. I can toggle Selinux(it doesn't turned on by itself any more) and I also can disable root and get the correct status. Thanks.

But I mentioned that the screen doesn't updated when the unroot period finishes. Needed to change orientation of device.

Device: Doogee Galicia X5

Android version: 6.0
[Magisk] topjohnwu:
The app_process unmounts after 20 seconds, it is impossible that zygote isn't initialized.

I suspect it is something with Magisk. Do Magisk itself break your phone? If so, please follow the bug report instructions so I can debug.
[Magisk] nlse:
how would the install procedure be, if i want to install magisk on a Samsung S3 i9300 and a Samsung Note 1, N-7000

do i have to go back to all original stockrom, or would it work with a stockbased rom?

there is only android 4. stock , on both i believe
[Magisk] SpasilliumNexus:
In OP:
[Magisk] DawoodSahi:
Nevermind, I forgot to install supersu app from playstore.

Everything is working perfectly.
[Magisk] :
Magical v3 worked like a charm on my s6 edge! Thanks a lot!
[Magisk] kraoc:
Hello,

I have an issue using v3... I tried to update to v3 with phh's root v2 and Xposed v86.4 and my rom stuck on boot.

I used the uninstaller and tried to reflash these things with the same issue...

I'm restoring a backup with twrp now...

PS: it's on i9505 LTE (works fine on my Tab S)

PS #2: 2 Samsung device and 1 fail... I don't know wy... and don't see the logs to provide :(
[Magisk] Cutieboy:
Flash "Magisk-v3.zip" on my Asus Zenfone Max with Android 5.0.1 (UL-ASUS_Z010-WW-12.8.10.82-user) and get "ERROR: Invalid boot image!" after reboot.

On Android 6.0 all was fine. Want to try "Magisk-v2.zip"- can't find download link.

Hot to restore backuped stock_boot[md5].img.gz?
[Magisk] Gosbo:
OK, thanks, hope it will work soon. There is too many updates of sn, it's hard to find how to bypass it now! Thanks for your work on xsetprop
[Magisk] andrew2432:
This works for lollipop? But you aren't sure about suhide?
[Magisk] zapahacks:
I looked at your screenshots but you seem to be using a different method, read the post and you will probably see that Magisk needs to be uninstalled. Did you do all the steps?
[Magisk] harpin14789:
Are cache modules still not working on magisk v8?

It just says that module activates after reboot but never activates.
[Magisk] dimm0k:
anyone else notice with Magisk v8 enabled that you can't attach files in the GMail app? can anyone else verify this for me? It took me a while of freezing all my apps to narrow it down to freezing Magisk that allowed me to attach files again...
[Magisk] vampire_8_7:
Hello everyone, has anyone else got safetynet failed I get [CTS profile match: false]. It was working till few hours ago, using Magisk v8.
[Magisk] yochananmarqos:
Yes, try reading a few recent pages before posting.
[Magisk] skidaway:
No problems here. Attached a photo and a zip to two separate emails.

Nexus 6/ABCrom (PureNexusMod)/Magisk 8
[Magisk] vampire_8_7:
I have already did this mate, but it's not a definite answer it's broken working for some and some others, this is why I wanted to see how many people are affected. :good:
[Magisk] Seanbest:
Running nougat here. Will this xsetprop help me at all? If so where can I grab it and find instructions? Searched, but just got pointed to this thread.
[Magisk] mathy007:
Yes confirmed it works for lollipop but for Su hide not tested because it states it's for 6.0+
[Magisk] 4RK4N:
cache mods cant be installed correctly with the latest manager. go to github magisk module repo, dl the module, re-zip it (git creates a folder in the zip, files for the flash zip need to bee in the top directory in the zip) and flash it in twrp. works fine here. have the zip i made 3 days ago. no new update so far.
[Magisk] SupDr:
Do Factory Reset remove Magisk ?!
[Magisk] mathy007:
NO it only remove the apk of magisk manager and phh super apk
[Magisk] izeeqo:
Magisk needs to be uninstalled? I've readed the post but i haven't seen that magisk needs to be uninstalled, and if i uninstall magisk... How phh superuser (root) will work without magisk? Because if i uninstall magisk, phh superuser (root) will also be uninstalled automatically...
[Magisk] AbiDez:
Everytime when I uninstall Magisk my handy don't boot... I'm not able to install SuperSu because when patching Ramdisc it comes abort... With stock boot.img it's the same, no SuperSu install possible.. When install Magisk my Handy boot... Is it possible that some files don't removed by Uninstaller and what is with the img files?

CarHDRom V.25 by Carotix S6edge
[Magisk] Apexpredator12:
Ok I managed to fix my problem I just reflashed my Stock MM ROM, and reinstalled V6 and phh-superuer-17-magisk and xposed v86.5-sdk23-topjohnwu, but when i reboot everything is fine but Magisk manager says that magisk isnt installed, my device still isnt rooted and xposed says that the firmware is installed but not active.

How can I fix this V8 won't seem to work for me so just back to V6 is fine, V6 is installed the folders and magisk.img is there but just doesnt seem to work
[Magisk] Captain_Throwback:
Will it help you what? You haven't said what you're trying to do.
[Magisk] Gosbo:
Hello all, i try to search a kernel who hide my unlocked bootloader htc10 but I don't find anything, maybe there isn't for HTC10 .. Still can't add card in Android pay since 2days for me, no solution work because getprop ro.boot.verifiedbootstate is orange.
[Magisk] Captain_Throwback:
ElementalX.
[Magisk] Lughnasadh:
The QPR2 Beta 1 build (without any modifications) does boot on the Pixel 6 series.

No, but you may need to if using a custom kernel.

For the Pixel 7 series, disabling both verity and verification is required to run custom kernels, although you can flash a custom kernel with these flags enabled (it won't boot), then wipe, then flash the custom kernel again with success. But of course this requires a wipe which users are trying to avoid so keeping verity and verification disabled when updating each month is the best way to go about it so you don't have to wipe (except for the initial instance where you disable those flags).

For the Pixel 6 series, although not required in most instances, disabling verity and verification can help to avoid issues, especially the red eio corrupt message (which is really innocuous but bothers many users), when updating builds, flashing custom kernels, etc..

But I digress...
[Magisk] Loustsoul:
17.35 MB file on MEGA

mega.nz

This is the thing I did for the clock to go away. I had to wipe and re-flash, but I tried dirty flash first but it stayed no clock.
[Magisk] Loustsoul:
17.35 MB file on MEGA

mega.nz

This is the hide clock thing that I used. I had to wipe and re-flash to get rid of it.
[Magisk] J.Michael:
Is that a Magisk module?

Have you looked inside to see if it's a pure "overlay part of filesystem", or if it has an install script?
[Magisk] Loustsoul:
I don't know what that means yet, but I plan to learn. 😊