yashsingh1/xdaforums huggingface dataset:
[Magisk] soadfan:
That's the problem. I'm not sure if the archive I downloaded is corrupted or if it's an entirely different problem.

The phone is brand new and it has no data yet because unlocking the bootloader will wipe it anyway (on Xiaomi you can use an official tool, but there's a "168 hours" cooling off period between starting the procedure and actually unlocking it).

About the other thing, I didn't see any recovery mode while patching, see attached.

EDIT: Just saw the ramdisk thing 😅
[Magisk] zgfg:
fastboot boot ... command must work

Double check if OEM is still unlocked.

And make sure you have updated fastboot/adb package on the PC

Again, I also have Xiaomi with dual slots, and the method (without worrying about ramdisk, vbmeta and WITHOUT messing with fastboot --set-active=...) always worked for me with MIUI 12 and 13, A11 and A12
[Magisk] soadfan:
It's the latest, 33 something, iirc

Just checked, and yep it's 33 something:

Android Debug Bridge version 1.0.41

Version 33.0.3-8952118

Installed as H:\android-sdk-windows\platform-tools\adb.exe

EDIT: Just tested the 11T PRO. And it's the same it won't boot if you try to change the active slot.
[Magisk] pndwal:
Did you ever boot to the inactive slot?... It's not clear what you ever installed there... A/B devices generally don't come with OS loaded on both slots... Guess device came with OS on A and you took OTA to B before attempting root?...

Maybe current A booting issue already existed?... PW
[Magisk] soadfan:
Well, I'm going for it. Fingers crossed.

EDIT: Yep, it's fine. I guess you weren't supposed to force a boot from the inactive slot anyway.
[Magisk] pndwal:
Yeah, I'd seen that issue... Is it from A13 beta 2 and related to vbmeta patching as a user suggests?... Are P7 users disabling AVB?... (Seems this issue might not affect P7?) PW
[Magisk] 4RK4N:
worked til a few hours ago. magisk_v8 phh root r259_magisk and the 2.1 manager app for magiskhide.

right now "CTS profile match: false"

or is that some yet unreleased version?
[Magisk] alexpower:
Not released yet

Gesendet von meinem HTC 10 mit Tapatalk
[Magisk] topjohnwu:
It has been a while since I do support replies lol

I hope I can spend some time each day to reply to this thread :)

Maybe the cache for the repos are messed up. Try to wipe the application's data.

This is an unreleased version, requires both new Magisk and a new phh's root update.
[Magisk] ert69:
SafetyNet got updated. If you read the thread u would know.
[Magisk] Apexpredator12:
I tried to install V 8 last night but it messes up my phone so I restored my backup and it's fine now, but for some reason my capacitive back button won't work. It lights up when I touch it but doesn't do anything doesn't even vibrate when I press it, I have read all sorts online but can't find anything to fix it does anyone have any solutions?
[Magisk] bigcid10:
if xset is installable and works without magisk

is it a different command or file

I tried to flash it in twrp and it errored out

Thank you
[Magisk] Captain_Throwback:
You have to do it manually, or you can try the zip posted here for SuperSU.
[Magisk] edyny1:
I'm following your steps but xposed 86.2 is not installing at all.
[Magisk] izeeqo:
How did you make your modules working with xposed disabled in root switcher please ? I've disabled xposed in root switcher but i can't use my modules... see screenshots
[Magisk] izeeqo:
How did you make your modules working with xposed disabled in root switcher ? For me xposed is disabled in root switch but i can't use my modules... see screenshots
[Magisk] DeadlyByNite:
The only reports of xposed not installing is if you are using Magisk v8 mod2. Are you for sure using the original Magisk v8?
[Magisk] izeeqo:
I'm using magisk v8 mod2 and for me xposed v86.2 is installed
[Magisk] DeadlyByNite:
It may work for some devices, and not others. I don't know of any other reason why xposed wouldn't install. It would be handy to have a log or a screenshot of the error you're getting.
[Magisk] Gosbo:
Hi, I have done a clean install on my htc10 with unlocked bootloader but I have a problem with xsetprop without magisk, it works before but now I have try to move xsetprop binary file and post-fs-data.sh to /su/xbin and /su/su.d and did Chmod 755 for each file via twrp and via terminal emulator with su enable but when I type getprop ro.boot.verifiedbootstate it was orange.. ? try to flash xsetpropSU from the link posted but still no work for me!

I don't understand why it works before with magisk
[Magisk] mrxtc89117:
Are you getting a error 1 on twrp install? If so, flash it using flashfire from the play store.
[Magisk] Vipriel:
Same here. When Xposed is in yellow state (only state that allows SafetyNet to pass and PoGo to work), Xposed modules do not work.
[Magisk] Tikerz:
How did you uninstall it? Did you just flash the uninstaller zip?
[Magisk] hokiealumnus:
Yep! I removed phh superuser via the magisk program, rebooted, booted into recovery and flashed the magisk uninstaller, then booted up and uninstalled the magisk app.

Don't forget to re-bump your boot image if you have a g3
[Magisk] bigcid10:
Thank you ,I flashed it and with the combo you suggested it's all green :D:D:good:
[Magisk] Captain_Throwback:
Because Magisk and SuperSU don't handle scripts the same way on the HTC 10 (it seems).

I have the same problem as you. Guess we'll just have to wait for the Magisk update...
[Magisk] pndwal:
Still, was A bootable before applying Magisk?... PW
[Magisk] soadfan:
Didn't try.

But tried on the 11T Pro and it wasn't - but it has Magisk and few OTA updates.
[Magisk] pndwal:
If never confirmed it was bootable before Magisk, how could you expect it would boot after patching?! 🙃 PW
[Magisk] soadfan:
idk, I just assumed this is the way it should work^^
[Magisk] pndwal:
Well if you moved to current slot after OTA, you'd be downgrading OS when moving back... If you had purposely loaded a new OS on that slot and tested it I could see the point... But then you could have installed Magisk on that as active slot anyway... PW
[Magisk] zgfg:
As answered you earlier in the morning, you shouldn't switch - but ok, now you know :)

I can only tell you (I checked in my mem and some private conversation), I tried once with Xiaomi.eu, also MIUI 13, and got bootloop, even fastboot boot did not work.

I tried then without patching, I just wanted to see if I could use one slot for root and the other without

If it worked for your older Xiaomi, fine, but for sure it was not necessary.

OTA manages the slots and assures that the active one is bootable. You just patch and flash boot.img for that slot

If you switch the slot, who knows what is there. Btw, didn't you have a log saying that the active slot was not bootable - IMO, it was not bcs you flashed the boot.img, but a flag telling Bootloader if the slot is bootable or bot
[Magisk] shoey63:
It started on A12 (after working initially) and persists through A13.

And I have never patched vbmeta. Besides, you can't take an OTA with a modified vbmeta (or any other) partition.

It seems Google has introduced a dm-verity check on the inactive slot somehow after the OTA and will return a "device corrupt" message when you try to boot to it with a patched boot image, and it will hang on the Google logo.

Only way out is to force a restart a couple of times to get it to boot back to the working slot or flash the stock boot image to the OTA slot.

Once booted to the updated slot, you can only then boot or flash a patched image to regain root.

I assume Pixel 7 users will face the same conundrum. Most root users just flash the factory images and patch boot.
[Magisk] pndwal:
... This convo went here:

https://xdaforums.com/t/discussion-play-integrity-api.4479337/post-87716153

PW
[Magisk] zgfg:
If it is only about switching to the other slot, use:

fastboot getvar all

to read the currently active slot and then switch by:

fastboot --set-active=a

or

fastboot --set-active=b
[Magisk] pndwal:
Ah... So user comment in issue may be a red herring...

Makes sense, thanks...

Mmm... Patch init_boot for P7...

🙂 PW
[Magisk] pndwal:
I think connecting a PC at all defeats the purpose of Preserve Magisk thru OTA w/ A/B Install to Inactive Slot method... It's to allow unattached OS update w/ Magisk root preserved... PW
[Magisk] zgfg:
This is Fastboot - and it requires the unlocked Bootloader

On my Xiaomi I switched the slot, got bootloop, switched backed and it was booting again with no consequences
[Magisk] pndwal:
Sorry... The issue related to the guide for OTA w/ A/B Install Magisk to Inactive Slot method causing bootloop... Not sure where fastboot comes into it... (Normal flashing patched image to active slot works fine for P6 w/ A13 apparently)... PW
[Magisk] zgfg:
Hunter: more fun guaranteed than with Momo (you will probably need to use Lens to translate to understand what it shows)
[Magisk] Nemosfate:
delete please
[Magisk] Ikarus01:
Hello everyone!

Thank you for the very active thread i finally managed to figure out what i did wrong (yet again).

I rarely tinker with the device, and when i am forced to, then i forget about A/B partitions, and wipe boot.img.

I was hoping there is now another way for keeping TWRP and Magisk. Aside from embedding twrp image in stock boot, and than patching from magisk manager?

Thank you.

Also if someone more knowledgeable could help (even though it is slightly Offtopic), do i patch boot img with firmware boot img, or boot img from the custom rom i was using?

Because that rom was then for testing (even though i kept it), and i can't figure out the version.

I suspect when i run adb shell getprop "ro.product.version" it will probably fail, because i did a number on that device trying to fix it without understanding A/B partitions.
[Magisk] zgfg:
Only if you don't have Recovery partition, then you patch TWRP to Boot (and afterwards the Magisk)

(It's not necessarily specific to A/B devices - there are A/B devices that do have separated Boot and Recovery partitions, and in that case TWRP goes to Recovery partition, Magisk to Boot)

But when you update Magisk, you can just take Direct Install (update)

---

And of course, you must patch the boot.img corresponding to your current ROM. Usually, you can find it in the ROM zip file

If you use some stock boot.img instead, then you risk the bootloop (of course, if boot img from your custom ROM coincides with the stock boot img then it doesn't matter, but usually it won't be the case - or you will not know

That does not depend on Magisk - if the boot.img is wrong and you flash it (with or without Magisk) it will cause the bootloop (in the 'better' case, it may boot but you might have troubles later because of eg the wrong Kernel).

Hence make sure to always use (for patching) the correct boot img
[Magisk] zgfg:
New Shamiko-v0.6(126)

With this new Shamiko, Momo does no more detect Zygisk and Zygote (official latest Magisk Canary 25205, Zygisk enabled, DenyList configured and not enforced, Shamiko v0.6 in default black-list mode)
[Magisk] huskydg:
Hide most traces of known detection. There are still some traces but momo doesn't detect them
[Magisk] dimm0k:
trying to USE magisk on a Pixel 4 XL with the October 2022 update and it's not working properly. installation of magisk works fine and I can use root apps, however as soon as I install a module and reboot the phone never boots up and just stays at the G logo. not even a fancy module, the default built-in systemless module causes this! help!
[Magisk] pndwal:
1) I assume you definitely downloaded, extracted and patched boot.img from October full ROM image (eg. didn't just reapply previous magiskpatched-boot.img after an OTA) to ensure properly matching system and kernel?

2) Systemless hosts was a key trigger for old f2fs loopback bug... Seems the issue persisted in Pixel 4 series and beyond... Just a guess, but looks like this may be your issue especially if Google never addressed to the bug in updates...

See this issue (long read):

https://github.com/topjohnwu/Magisk/issues/3171

and qualified comments like this:

https://github.com/topjohnwu/Magisk/issues/3171#issuecomment-729814931

and

https://github.com/topjohnwu/Magisk/issues/3171#issuecomment-732370526

Nb. Patched / custom kernels can fix this issue; seems Google wasn't particularly interested (bug basically only shows up for Magisk users...). PW
[Magisk] traversone:
just tried Shamiko 0.6(126) but the Magisk's module page says "shamiko file is corrupted, download from official sources" (or something like that) ! Infact it does not hide root on the same identical system
[Magisk] dimm0k:
yep, pretty certain since I didn't have any magisk patched kernels since I flashed the October ROM completely. anway, damn, this is crazy! finally resurrected my P4XL after about a year and recall when I was actively using this device that Magisk was fine... thanks for this info, will have to seek some kernel/ROM alternatives
[Magisk] pndwal:
It would pay to be very certain of point 1)... Flashing a recent boot.img often works but invariably causes issues...

Other Pixel Users (especially 4XL):

Can anyone confirm if loopback bug is still an issue w/ latest stock kernels?... I'm not certain it is, nor what is latest kernel version (this affected kernels at least up to v4.9), but I notice the following fix (from linked issue) is still being merged almost daily in custom kernels for a plethora of different (incl. non Pixel) devices:

Spoiler content hidden.

🙂 PW
[Magisk] pndwal:
Fine for me... Did you download or take update in app?...

Try downloading again from here:

https://github.com/LSPosed/LSPosed.github.io ... PW
[Magisk] zgfg:
S-Check:

Security Check - Device compli - Apps on Google Play

Check your device readiness and compliance for Mobile Payments

play.google.com

Root detection, as on the screenshot

I can pass with Delta but cannot with TJW Canary

Delta:

latest, Zygisk, MagiskHide, no Shamiko, App Data Isolation, HMA

Canary:

latest, Zygisk, DenyList, Shamiko, App Data Isolation, HMA, even with Magisk app uninstalled

I have tested thoroughly on my two Xiaomi phones, one with A11 and the other with A12.

Tested on both phones with Canary and with Delta - and I have the same results on both phones

Not to mention that I fully pass Oprek, Ruru, TB-Checker, SafetyNet/Play Integrity
[Magisk] martyfender:
Your screenshot shows that it passed. It is red when it fails. I believe I have this correct, even though the wording is confusing, it is backwards. If I am wrong please correct me.
[Magisk] pndwal:
Yup, Native bridge loading based on Maru Magisk fork implementation of Riru's loading method seems to have much merit...

Nb. Original author says it's an experiment however, still not perfectly implemented and may be issues w/ some modules... Also Shamiko hiding with probably not work properly with this... Long read here for those interested:

https://github.com/5ec1cff/my-notes/blob/master/maru.md

For others, I put more here too:

https://xdaforums.com/t/discussion-...third-party-magisk-fork.4460555/post-87729841

🙂 PW
[Magisk] pndwal:
Yes, he's passing w/ Delta / experimental Native Bridge Zygisk loading... PW
[Magisk] 73sydney:
Worth pointing out that @zgfg asked me to test that on Magisk Canary (official) earlier but ive broken something it seems with my uber Samsung debloat and cant get S-check to even open anymore :)

Anyone else care to chime in with Magisk Canary (official)
[Magisk] martyfender:
I have 2 Onn 8 first gen tablets on Android 9. On one I have the latest magisk canary build on it and s-check passes the root test. On it I have the latest zygisk lsposed, shamiko and hide my applist configured.

On the other tablet I have the latest magisk canary delta with magiskhide with it's hide list configured and zygisk disabled,riru lsposed, riru unshare, momohider and hide my applist configured also. In addition, the root check passes in s-check, on it.

Furthermore, I have USF on the official magisk canary and USF mod by displax on the delta build. Safety net and the api basic integrity pass on both. Finally, all exposed module are hidden in tb checker, applist detector and oprek.
[Magisk] ayush_dey:
Will Magisk support EROFs?? As PE 13 for my Pixel 3a is on EROFs so Magisk is not working
[Magisk] zgfg:
As I said, I pass on Magisk Delta (an unofficial Magisk fork), does not pass on TJW Canary

I took the screenshot from Delta, where passing

The point for screenshot was to show what I was talking about (since S-Check is seldom mentioned here)

But ok, if necessary, the new screenshot below shows how it looks when it fails for me on the Canary ( there is an 'error' code for the detected root but we don't know the meaning of its info codes anyway)
[Magisk] traversone:
just using the ZIP downloaded from their official source...I mean to say the issue is not solved. Ayone could identify which issue (on my system) triggers that error?
[Magisk] chichino84:
Hi everybody!

I'm having problems with my phone, freezing few seconds after booting and then restarting.

Already uninstalled Magisk along with all modules, no luck.

Also tried to flash the original boot.img via fastboot command, but it seems that it is flashed only on the slot "a" - while (if I remember correctly) the Magisk patched boot.img was flashed on slot "b".

Is probably this the part I'm doing wrong? Should I flash the original boot.img on both partitions by the command "fastboot flash --slot=all boot"

Please bare with me, been away from rooting since a loooong time....

Thx!

Pixel 6a

Android 13 (nov. update)

Magisk 25.2
[Magisk] rodken:
It might be considered over-kill, but you could just switch to the active slot and run the command again.

As a precautionary measure, I would recommend booting into the OS after the first flash to make sure it flashed ok. If there happens to be an issue like a bad flash you want to be sure that the "other" slot is bootable or you might wind up with a pair of unbootable slots.

fastboot flash boot_a name_of_boot.img
fastboot flash boot_b name_of_boot.img
[Magisk] chichino84:
Thx for your answer.

Tried to boot through both slots (after verifying with "fastboot getvar all") and result is the same: it boots fine, but freeze & reboot after few seconds.

What other options I have? A fastboot factory image flash?
[Magisk] J.Michael:
Was it working just fine, with Magisk installed, and after weeks it suddenly had a problem?

Did you take an update? Did you uninstall Magisk first?

Have you been following this thread enough to notice whether your device/ROM is one that suddenly needs something other than boot.img patched? (Something like "init_boot.img".)
[Magisk] kerlaeda08:
tell me what to do please, put tvrp and magisk, everything seems to be normal (there is a root), but after rebooting the phone, a lock screen appears asking you to enter a pin code and a black background (that is, there is no splash screen) and when you enter the pin code, the phone will not be unlocked for a long time (all also a black background and no desktop) and again a black screen with a pincode input. sometimes the desktop appears for a second, but then a black screen and again unlocking. only wipe in tvrp helps to get rid of this. Smsung A50 stock
[Magisk] rodken:
I missed the part where you attempted to factory reset your device.
[Magisk] kerlaeda08:
resetting to factory settings helps to remove the permanent lock screen, but if you install Magisk again, then after the reboot there will be a lock screen again
[Magisk] chichino84:
It was working fine until I installed Pixel Launcher Mods module, issue started right after the activation reboot inside the Magisk app.

So I tried to clean everything back from there. Along with the app itself (completely uninstalled as 1st thing), other modules I've uninstalled are AOSP Mods, Zygysk and Systemless Host.

Haven't done any recent update, last OTA I installed is November, all seemed works fine till today.

Android 13 stock on Pixel 6a doesn't have init_boot.img file to be patched.

EDIT: turns out it wasn't any module to cause my issue, it was the Greenify app messing with my Smart Lock settings right after boot. Uninstalled - along with its root privilege- seems to have solved everything.
[Magisk] rodken:
Did you try this method for your device [outdated, but still reliable]?
[Magisk] dimm0k:
my steps were essentially the same I take to update my Pixel devices

- download the full factory image

- unpack its contents

- unpack the boot.img from the large zip file from the contents

- feed magisk the boot.img, save it to the computer

- fastboot flash the resulting file from magisk

did I miss anything else or do anything wrong?
[Magisk] J.Michael:
Try "fastboot boot" the unpatched boot.img -- just to make sure it works. (If you've been recovering by flashing the unpatched boot.img, just ignore me.)
[Magisk] pndwal:
No; your process seems good as long as you're sure you didn't mix up older .img files on PC etc...

It would be good if P4 series Pixel users could confirm if loopback bug was never fixed w/ updates... But it's certainly looking like this... PW
[Magisk] dimm0k:
given that the Pixel 4XL has reached EOL in terms of Google updates, perhaps I'll move entirely to the PixelExperience ROM where there's more support. thanks for shedding the light on this bug!
[Magisk] ipdev:
I had that issue a while back, I do not remember what I did to fix it. :unsure:

I just setup my Pixel 5a (it did not like updating from July to November 🙄) so clean flash. 😛

No issues with Security Check. 🙂

Pixel 6 - Stock Google 12L (July 2022).

Pixel 5a - Stock Google 13 (November 2022).

Magisk debug (snapshot)

- Personal build from the official branch, so it includes the commits since the last canary/debug release.

Magisk - [GitHub] - Building and Development

USNF - Not the one that includes Displax's changes.

- Personal test build that includes some other (mostly prop) changes.

Fork - [GitHub] - commits

One of these days I will have to pull Displax's Zygisk changes. 🙃​

MHPC

- Set fingerprint back to stock Pixel 12.

Pixel 6 is using the Pixel 6 12 print, 5a is using the 5a 12 print.

Shamiko and LSPosed modules.

HMA (Beta v3.0.5 r373)

Two templates.

Magisk

- Settings (renamed Magisk app).

- Hide My Applist.

PlayStore

- YouTube

- YouTube Music​

AdAway running in VPN (non-root) mode. ;)

Cheers. :cowboy:
[Magisk] pndwal:
Good stuff... It would be useful if you could put your finger on what's needed to pass S-Check w/ TJW Magisk... Clearly Maru Magisk Native bridge loading isn't needed for this detection... PW
[Magisk] 73sydney:
Its all good, i picked up a Pixel 6 Pro this afternoon, i thought it might save any more posts on XDA about how fed up ive become at Samsung trying to dictate how i use devices i paid them for, and specifically how they keep breaking my ability to easily connect my phone and watch. Had enough, back to Pixel...

Already feeling less stressed...want to unlock your bootloader?:

Samsung - We'll make you wish you hadnt even thought to try, go any further and we'll ruin your life and void your warranty

Google - Heres how you do that, plus you can keep your warranty. Have at it...
[Magisk] pndwal:
FWIW, LoveSy (Shana) has made a pull request for Zygisk v5 Api already merged in her Metagisk ('The Meta Magic Mask for Android') Magisk fork... The commit Add inode plt hook APIs includes this comment:

John has requested new XHook API use with Zygisk be deferred (stay w/ v4 for now) and Shana suggested fixing v4 Zygisk compatibility (Zygisk crashes whenever a module uses v4 api, see fixes #6402 and #6396) issue before revisiting this PR (it's been marked as draft for now)... This may also explain some recent Zygisk issues... Watch this space...

I have no idea about inode plt hook or what benefits it will bring... Any coders w/ XHook experience care to edify us? 😃

CI Metagisk build is in Artifacts here (for mavericks):

Add inode plt hook APIs Magisk Build #2276...

👀 PW