yashsingh1/xdaforums huggingface dataset:
[Magisk] zedogas:
Same to the last asus zenfone 7 firmware 31.0210.0210.309. The patched "boot.img" doesn't work anymore. 😩
[Magisk] Lughnasadh:
Rooting shenanigans on the Pixel 6 series running QPR2 Beta 1 apparently being looked into.

https://twitter.com/i/web/status/1602774339224367104
[Magisk] Ștefan Radu:
So I need some help :( Today, after installing a Magisk module my phone got stuck into bootloop. What I've tried so far:

deleting the faulty module

deleting all modules

magisk remove-modules

reinstalling magisk

dirty flashing rom

reflashing ROM boot image

booting into safe mode??? (doesn't work)

reflashing recovery

angrily staring at the wall as nothing works

An obvious solution would be to wipe everything and install the ROM from scratch, but that's not really a good option, as I want to keep my data. From what I've read online, the device has the data partition encrypted at startup but I don't know what to make of that. I can access the device via adb while booting, but everything is readonly. Also, when Magisk is installed I can get root access with `su`. I'm open to any suggestions.

Device: Samsung Galaxy S10e (beyond0lte) Exynos CPU

OS: LineageOS with MicroG

Recovery: Lineage Recovery

PS: I don't know if I posted this in the right place. Correct me if I didn't.
[Magisk] zgfg:
Be aware that the problem for that Beta Pixel update is very specific - it was described further in the discussion (as well as the solution was posted)

Of course, there is always a slim possibility that you have the same issue on your Zen phone, but there could be other reasons for "not working", specially if one does not even describe what does it mean (not booting, booting but Magisk app not finding Magisk, etc), and without additional info about the Android version, etc
[Magisk] J.Michael:
If the bootloop started when you installed a Magisk module, then removing the module should have fixed it. If you tried to remove or disable the module, but that didn't fix it, I think you should have tried harder -- make sure you really removed the module before flailing around doing everything else you could think of.

I do not understand "when Magisk is installed I can get root access with `su`."

Are you able to boot now?

If "dirty flashing ROM" means you reinstalled the stock ROM, were you able to boot at that point?

When you say "booting into safe mode" doesn't work, how doesn't work? It was supposed to be: boot into safe mode, reboot, at that point you would have Magisk but no modules enabled -- just for that one boot. If you've already replaced the boot image that used to have Magisk installed, I don't know what safe mode could accomplish. But it should still be possible to boot into safe mode.

Maybe forget what you've done, just describe the current state of the device: what software you think is installed, and whether you can boot.
[Magisk] Ștefan Radu:
I am not able to boot. I wasn't able to boot at any point in the process.

The last thing I tried was reflashing the Lineage recovery and then dirty flashing the stock ROM.

I am able to access recovery, and get a shell into the device while it tries to boot up.

What I was reffering to "getting root access" is the following: If I would sideload magisk apk on top of what I've got right now, I could use `su` in the adb shell to get root (which is the expected behaviour I suppose)
[Magisk] dr4go:
The only thing that comes to my mind... has your data partition the full size or has it been shrunk to 32GB? Otherwise... I really do feel for you... I wasn't able to recover from my bootloop last year (S10 user). My new phone finally arrived... so I need to prepare a long overdue post...
[Magisk] Ștefan Radu:
beyond0lte:/ $ df -h /data
Filesystem Size Used Avail Use% Mounted on
/dev/block/sda31 109G 27G 82G 25% /data/user/0

Seem like the data partition is 109GB.
[Magisk] Ștefan Radu:
do you have any suggestion on what I could be the issue and what I could try?
[Magisk] kerlaeda08:
hello, got a root on a samsung a 50, everything works, but there was a problem. the screen auto-rotate works in the system itself, but it does not work in applications (for example, fb reader) the firmware is standard (11 android)
[Magisk] dr4go:
In case some of you want to read this, but would otherwise overlook it, sorry for the offtopic: https://xdaforums.com/t/time-to-move-on.4529985/
[Magisk] pndwal:
... Can you say Magisk module?... Might help... PW
[Magisk] Ștefan Radu:
safteynet fix 2.2.1 (https://themagisk.com/universal-safetynet-fix/) 90% sure. if not 2.1.3. I didn't properly read the docs, so I didn't realize that my phone didn't match the requirements (Magisk Canary installed / Riru)
[Magisk] pndwal:
... Interesting setup... I'm wondering about MicroG... Never used, but I know users needed some droidguard substitute + other gms components to allow S/N to work at all... Normally S/N (and new PI) integrity attestation is loaded with Google Play Services, so you won't have S/N API w/o GApps...

I'm wondering if there may be some fatal exception or error caused by USNF interaction w/ the minimal MicroG gms core/modified (incompatible?) components, or perhaps with your particular MicroG setup... Generally never seen bootloop w/ USNF even due to wrong version loaded... And I know some have again been passing S/N w/ recent MicroG builds after being S/N fixes being broken for a year or so...

Anyway, removing module should have sorted that...

Also, was thinking dirty flashing ROM probably won't remove Magisk in your case unless rom includes LOS recovery because I think you use Recovery mode Magisk (Magisk in recovery ramdisk) as it's A-only legacy SAR... Please say if I'm wrong...

Anyway, seems you have now flashed unpatched LOS recovery; that should have meant images are all stock...

If you actually meant you re-flashed Magisk-patched recovery (ie. still have root), device may (still) be bootlooping due to corrupt magisk.db/other configuration files... In this case, flash original unpatched LOS recovery... That should restore bootup... Next, delete all contents of /data/adb before reinstalling Magisk... Could boot-only TWRP (shouldn't need to flash) which can decrypt/see /data unlike LOS Recovery...

Hope this gives some clues... 🙃 PW
[Magisk] pndwal:
Want native Support extract boot image from payload.bin?... 👀 🙂 PW
[Magisk] rodken:
Are you searching for a method to extract or are you asking for something else?
[Magisk] zgfg:
Sorry, didn't study deeply to the merge request, what would that be - that user could patch by pointing to payload.bin instead of extracting himself by eg Payload Dumper and pointing then to the extracted boot.img?
[Magisk] Mr. V.:
Hello!

I have a big problem.

I'm installed latest Magisk, added Island and my bank apk not run: root detected.

Replaced to earlier patched Magisk 23.0 version boot.img and reinstall 23.0 Magisk apk. (Uninstalled with TWRP, reboot to bootloader, upload img, install Magisk.apk and Riru and LSPosed.)

Changed LSPosed to Riru version. Now bank apk working correctly only on Island... all other function confused.

In Island runned HWinfo and say: ROOTED. The Bank software running normally. How is it?

Another malfinction for example:

After install any apk file, "Android System" notification say: "Incompatibile with current system version". ALL!!!

The Total Commander run from Android 2.3 - latest android version. NOT incompatibilie! (Now my android version: 8.1)

The "Network Signal Info Pro" worked earlier, now not. Started, and closed in 1 sec. Widgets half working (wifi ok, but slow, mobile not read correct info). Installed latest version, not modified, clear cache+davlik, same problem. All installed apk really compatibile this system. Earlier running correctly.

Another problem:

WebView implementation:

Listed:

"Andrtoid System WebWiew" (stock)

"Andrtoid System WebWiew" (108.0.05359.128)

"Chrome Stable"

"Bromite System WebView"

After selected another, not stock:

"The choice is no longer valid. Try again."

Installed under LSPosed (downgraded 1.8.4 (6609)) "AnyWebView / Any WebView is OK!" 1.1 module and enabled, ticked:

System Framework (Recommended)

Android System WebView 99.0.4844.51

Bromite System WebView 108.0.5359.109

Island 6.0.5

Same problem, not selectable another, only the stock (not work for exampe vodafone webpages).

The phone (Huawei P20 Pro with stock 8.1 android version) google free (deleted)! Not have Google Play, etc. Installed all softwares manually with apk files.

Another more apks working, only 1-2 not.

Where do I look for the fault that is causing these 2 problems?

"Incompatibility" is a more important problem than WebView, so I would look for an answer to that first.

The earlier good condition:

Magisk 25.3

Not Riru

LSPosed Zygote version

No Island

(Banking not working, any installation workig correctly.)

No another modification.

Attached Magisk and LSPosed logs.
[Magisk] Mr. V.:
Dropped "magisk_log" attached file, reupload not work. Uploaded here: https://workupload.com/file/mAeDC5NB7Xr
[Magisk] J.Michael:
Did the screen rotate work before you installed Magisk?

Are you sure you are looking at apps that rotated before you installed Magisk?

I have auto-rotate enabled. Some apps ignore it. Not a lot of apps, but some.
[Magisk] J.Michael:
I don't know "Island". Did you do something in Island to hide root from the bank app? Did you do the same thing in Island to hide root from HWInfo?

All these horrible things happening: are they only happening in Island?

Have you tried uninstalling Island?

Maybe you deleted one too many Google apps. Can you reinstall the stock ROM and start over? Maybe leave the debloating until everything else works.
[Magisk] kerlaeda08:
unfortunately yes ((I always used this reader and auto-rotation worked (in another reader, the same situation)
[Magisk] Displax:
Native extract from payload during boot patching. Could be preparation for P6(A) on QPR2.

Interesting assumption, can anyone trying to patch boot.img from payload.bin instead of factory image?
[Magisk] pndwal:
Sorry if ambiguous / seemed flippant... Question was rhetorical... Just an observation/PSA that we may be getting native support for this in Magisk...

@Displax has answered this above... May only be initial support commit at this point, but may already work like that... Clearly main function is do_extract_boot_from_payload...

If anyone wants to test, CI build is in artifacts here:

https://github.com/topjohnwu/Magisk/actions/runs/3683249649

🤠 PW
[Magisk] 73sydney:
Sorry, not touching that one beyond this post, way too much going wrong there, mostly user caused

1) Google Play (removed) - theres half your issues right there.

- Install stock ROM

- Root with Latest Magisk

- Install USNF Mod

- Airplane mode on,

- Clear Google Play Services & Google Play Store data

- Reboot

- Airplane mode off

- Check integrity test

Then move on to banking software, we're here to assist with a sane functional working base

Island is probably/arguably entirely unnecessary

Why make life harder?
[Magisk] 73sydney:
Devils Avacado....

Isnt payload.bin large? (excuse me as i havent flashed a ROM using one for a while), granted from memory not as massive as a Samsung AP file....

I was never a fan of the method for Samsung of copying the entire massive 5Gb+ AP file over to device for patching, over extracting the boot image from it viz 7zip...one took 30 seconds of work to patch, the other a good 8+ minutes....

Me personally, i would rather use a payload dumper on a PC to extract, then move boot to device for patching, same as above Samsung PC arrangement. I get the attraction for convenience or if you needed to do it all on device. But it wouldn't be my 1st choice personally.....
[Magisk] ipdev:
A little above what I know, plus I am not that familiar with this part of Magisk. 🙃

Reading though it though..

I am left with the impression it might be more for OTA/Update instead of general patching. :unsure:

Interested to see what happens with it though. 👀

Cheers. :cowboy:
[Magisk] ipdev:
Not always. ;)

The payload.bin file is just a compressed file.

Depending on the device, stock and custom roms use a payload.bin file.

I have shared and mentioned in the past, I switched to using Lineage's scripts for unpacking OTA/ROM files.

If a payload.bin file.. [Github] - Line 62

I need to clean up the explanation (and instructions) in that script's header. :rolleyes:​

Cheers. :cowboy:

Edit:

Found a prior post. 🙃

Post # 44,443
[Magisk] ipdev:
Cross post from a different thread.

More appropriate in this thread. 🙃

To complicate it a bit.. ;)

New commit.

Cheers. :cowboy:

Spoiler content hidden.
[Magisk] m0han:
FYI for people looking for modules: https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-87860995
[Magisk] pndwal:
Perhaps, but I doubt it can help for traditional OTA update (Over The Air)...

If you did mean a new fix where boot image is extracted from an OTA payload presumably before update engine runs for patching when Magisk is reinstalled, I notice that the commit files contain many references to delta payload (definitions etc), but if this:

"delta payloads are not supported, please use a full payload file"

from line 77 here:

https://github.com/LSPosed/Metagisk...0513cca110268a766a178a/native/src/boot/lib.rs

applies as seems reasonable, it will still require downloading full OTA/ROM containing large (guessing) payload bin files rather than small differential/incremental (delta) payloads...

Seems to me it'll be just what it indicates: native ability to extract boot image from (full) payload.bin ROM archives...

I doubt you did, but if you were meaning recently failing 'preserve Magisk thru OTA w/ flash to inactivate slot method, I don't think can fix that as it's an issue where google introduced new checks where the update_verifier program reads dm-verity devices to make sure partitions aren't corrupted after reboot... A fix would involve partition digest being overwriten to account for Magisk binaries)...

@Displax's comment

is not particularly specific, but seems correct...

Re. this however:

I actually doubt it has anything to do with fixing the P6(A) on QPR2 rooting issue...

Can't root Pixel 6a beta android was posted 2 days ago (TJW is now soliciting help re. this on twitter; ...there is simply no root after flashing Magisk over this update... Seems if Clean flash full ROM users are successful however... Many have been flashing P7 magisk-patched boot.img on P6s successfully also... 😜) and so was Shana's Support extract boot image from payload.bin PR...I'm thinking she would have spent some time (days?) on this LSPosed/Metagisk 'payload' branch privately too... And she first commented in Can't root Pixel 6a beta android Issue only yesterday...

... I suspect it'll turn out to be something similar to sbin not accessible issue (Canyie's fix merged but not built in any release) myself. 😬

Yup... Shana may be the new vv!... Expect Canyie's name to show up on Magisk App home page any tick of the clock too... (Team Magisk 's becoming a bit like Charlie's angels!)

😝 PW

PS Howard Wu likes Shana's mind...

Refactor magic mount by unsharing magiskd...

...

The advantages are as follows:

1. it is more compatible, (e.g., with overlayfs, fix topjohnwu#2359)

2. it can mount more partitions for which previous implementation cannot create mirror mount points (fix topjohnwu#3338)

Can I suggest No. 3?...

3. Sniff test result: smells good for hiding... nuff said...

Interesting fork:

https://github.com/Howard20181/Magisk/commits/test

...
[Magisk] Mr. V.:
All my phone google free. After install root, immediately delete all google soft.

The magisk 23.0 rooted phone worked 1 year with running bank software. Now fully halted the system (no boot system or recovery), reflashed, installed latest Magisk (not earlier good working 23.0, new 25.3) and restored all (128) earlier installed apks. Not downloaded again updated version, used the earlier downloaded (and working) versions. (Earlier working all!)

Despite your request not reflash completly (128 software configuring all permission more than 4 day).

Uninstalled Magisk, reinstalled latest + zygisk LSPosed + XPrivacy + USNF and working my bank soft without problem (without Island).

Thanks!

If Island running, Network Signal Info Pro apk not working. (Not installed Network Signal Info Pro to Island, only real system.)

After uninstalled Island, this soft working correctly with widgets, no freeze.

Thanks!

Webview change still not working... SOLVED!

Disabled the "work profile".

Android Enterprise Help

Official Android Enterprise Help Center where you can find tips and tutorials on using Android Enterprise and other answers to frequently asked questions.

support.google.com

"Android System" notification still say: "Incompatibile with current system version" after any apk install.

The installed and notified softwares running correctly. Fake alert.

Any solution to this?
[Magisk] amritpal2489:
Can somebody provide me Pixel 7 Pro's magisk patched boot img from the latest QPR2 Beta 1 update?

The one which succesfully roots the Pixel 6 Pro
[Magisk] pndwal:
Why don't you download P7 Pro QPR2 beta 1 ROM, extract boot.img and patch it yourself?...

Nb P7P users are not extracting boot.img w/ kernel for Magisk patching anyway; they extract init_boot.img which has the generic ramdisk...

You need P7P boot.img which lacks ramdisk (as you likely know) for patching with P6P... Magisk manually adds the basic g-ramdisk needed for P6P when you patch...

I think you get QPR2 betas here:

https://developer.android.com/about/versions/13/download

🙂 PW
[Magisk] Ștefan Radu:
Hi! Thanks for the ideas. After trying stuff for the past few days I'm sad to say that I didn't manage to fix it.

Regarding the recovery, what I flashed was stock Lineage Recover and that didn't fix the bootloop.

Another thing I tried is boot-only TWRP. Unfortunately Samsungs don't really seem to have a working fastboot mode and I can't boot directly intro TWRP without flashing. So I flashed TWRP and sadly noticed that it doesn't decrypt /data. After more research I found out that I should be able to decrypt by running

twrp decrypt <pattern pin>

, but that fails with "No crypto support was compiled into this build" :(

I've got no other ideas really...

Is there anything else I could try to recover the data? That's my main concern right now.
[Magisk] J.Michael:
Try to find a TWRP build into which crypto support was compiled?
[Magisk] kerlaeda08:
Hi. after a normal reboot of the phone (samsung a50) not from magisk, when you turn it on, the unlock screen appears, but when you unlock the black screen and again the lock screen. and so endlessly
[Magisk] pndwal:
So Magisk is in recovery mode (patched recovery)?... (I believe this phone can be rooted w/ recovery or boot modes)... Does it boot to system via recovery propery (ie w/ recovery key combo and keys released at splash screen per Magisk Installation Instruction, Magisk in Recovery section)?

Did you patch boot image also, eg if you ever used .zip installer or took Direct Install w/o Recovery mode selected etc? What other mods have you made, especially before this issue started?

And please give ROM, android version, installation method details... PW
[Magisk] Lughnasadh:
https://twitter.com/i/web/status/1604408246109863945
[Magisk] pndwal:
Are you flashing latest official TWRP?; I'm guessing it should decrypt/data...

I note John's cautions for Samsung SAR include:

... So please don't do that!... Nb. I'm unsure if this has a bearing on flashing unpatched TWRP, but I suspect this issue won't be fatal (require full wipe)...

Also, I hope you did this (required when not pre-rooting a custom recovery Image):

https://twrp.me/samsung/samsunggalaxys10e.html

(...If you didn't, I'm guessing this may account for current bootloops?...)

Are you Odin flashing a TWRP .tar image, eg. twrp-3.7.0_9-1-beyond0lte.img.tar per "Odin Install Method (No Root Required)" section?

... Hope this helps either getting TWRPs w/ data decryption or restoring boot if vbmeta was the issue...

Nb. If you are forced to wipe data to restore system after recovering data w/ TWRP, I would

root twice again

per official TWRP instructions if installing Magisk patched custom LOS recovery or TWRP again:

First, restore latest stock ROM w/ Magisk root by patching AP.tar with recovery mode selected and flashing magisk_patched.tar as AP, together with BL, CP, and CSC (ensures clean install / full wipe / no configuration conflicts / latest factory firmware etc but w/ root)... DON'T use mtp for transfers!... Then, after successful system bootup w/ root (via recovery), pre-root a recovery .tar image and flash per "Odin Install Method" section... Ensure first boot is to custom recovery to prevent stock system overwriting it. Adapt above process (ie. flash other binaries along with patched_AP.tar or use other image types provided) if installing a custom ROM...

Hope it helps/ gives some clues... 🤠 PW
[Magisk] kerlaeda08:
phone - samsung a50, 4g ram, 64g internal memory. I flashed twrp with odin, installed Multidisabler-Samsung-3.1.zip in twrp, then updated Magisk to version 25.2. the phone normally reboots from the magisk application, the problem occurs only if the phone reboots without magisk (the problem can only be fixed using wipe data)
[Magisk] pndwal:
What happened?

Testing this:

https://twitter.com/i/web/status/1604408246109863945

Media above gets hidden!? But it's still embedded... Was it bogus? A prank?... Twitter killed it / Google had it removed?

This makes code appear:

MEDIA=twitter]1604408246109863945[/MEDIA

Not sure now if official Device Integrity / Developer Options menus are real or Photoshopped now... I now have version 33.6.13-21 [0] [PR]... I certainly don't get those options as posted...

Here are posted/removed images:

... Perhaps leaked images from an internal Google test version? 🤔... PW
[Magisk] V0latyle:
yeah, looks like they've not only been removed, but gone completely dark
[Magisk] Lughnasadh:
Apparently that Twitter account no longer exists. Have no idea why.
[Magisk] 73sydney:
Maybe TopJohnWu killed him

i imean anytime something happens at Google people assume Johns involved and its the worst possible outcome, so this would be totes on brand for half the XDA crowd...
[Magisk] Lughnasadh:
I highly doubt it was bogus, a prank or photoshopped. Mishaal Rahman has tweeted about that person's "feature discoveries" before and those were legit.
[Magisk] bege10:
After upgrading /e/OS (based on LineageOS) on my Fairphone 3 (with TWRP and Magisk) from Android 10 to 11 Zygisk is not active although the respective switch is activated.

I upgraded the ROM via adb sideload

booted the system once, then

restored TWRP

flashed Magisk 24.2 in TWRP

Now it is not possible to have Zygisk active.

I toggled the switch and rebooted several times

removed the modules that need Zygisk

later installed the canary build

Nothing helped.

Is this a known issue?

What can I do to solve this issue?
[Magisk] rodken:
Usually, it could be a mismatch between the Magisk app and Magisk binaries versions.
[Magisk] bege10:
Magisk and Magisk app have the same version number (25205).

How to disable verity and encryption? Will that result in data loss?
[Magisk] pndwal:
If you've been messing much with Magisk, eg downgraded, switched between TJW and unofficial or CI builds etc (and sometimes w/ just official), Magisk configuration in /data/ADB (possibly just magisk.db) may have been corrupted... Just delete everything in /data/ADB and reboot, reboot and Magisk daemon (magisk.d) will rebuild config files; Nb. You'll lose all modules and settings incl. Superuser list and denylist, so note yours first to set up again... (Can try keeping modules if familiar with the file structure.)... Also, may take 2 reboots to fix Zygisk...

This fixed the same issue for me after moving back to official Canary from a Shana 'Metagisk' test build (which was working fine) recently...

Note; Some custom kernels are incompatible with/break Zygisk... This may be the issue with your /e/OS build... Could check what changes Gaël makes to LOS kernel. 😉... PW