Magisk General Support / Discussion

[m_pastuszek]

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

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

 

[pndwal]

Just catching up, n very interesting solution...

@zgfg flashing pathed boot.img and vendor_boot.img don't work too.

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...

We found 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

...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

 

[Lughnasadh]

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

The sources are extremely similar.

 

[m_pastuszek]

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

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.

 

[Lughnasadh]

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

The QPR2 Beta 1 build (without any modifications) does boot on the Pixel 6 series.

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

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...

 

[Loustsoul]

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.

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.

 

[Loustsoul]

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.

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.

 

[J.Michael]

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.

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?

 

[Loustsoul]

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?

I don't know what that means yet, but I plan to learn.

 

[zedogas]

@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.

Same to the last asus zenfone 7 firmware 31.0210.0210.309. The patched "boot.img" doesn't work anymore.

 

[Lughnasadh]

Rooting shenanigans on the Pixel 6 series running QPR2 Beta 1 apparently being looked into.

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

 

[Ș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.

 

[zgfg]

Same to the last asus zenfone 7 firmware 31.0210.0210.309. The patched "boot.img" doesn't work anymore.

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

 

[J.Michael]

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.

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.

 

[Ștefan Radu]

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.

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)

 

[dr4go]

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)

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...

 

[Ștefan Radu]

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...

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.

 

[Ștefan Radu]

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.

do you have any suggestion on what I could be the issue and what I could try?

 

[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)

 

[dr4go]

[...]My new phone finally arrived... so I need to prepare a long overdue post...

In case some of you want to read this, but would otherwise overlook it, sorry for the offtopic: https://forum.xda-developers.com/t/time-to-move-on.4529985/