Magisk General Support / Discussion

Search This thread

zgfg

Senior Member
Oct 10, 2016
7,814
5,226
...
In this context it's obviously just an expected and logical update to these previous notes about pending removal of MagiskHide in Alpha specifically:

😅 PW
Regarding to:
> According to telemetry data, the number of zygisk users has reached 78.3%, and after more than 85%, alpha will remove magiskhide

Btw, I'm not sure if I ever read they really reached that 85% target (they were slowly approaching 80%), but now it's not important
 

pndwal

Senior Member
Regarding to:
> According to telemetry data, the number of zygisk users has reached 78.3%, and after more than 85%, alpha will remove magiskhide

Btw, I'm not sure if I ever read they really reached that 85% target (they were slowly approaching 80%), but now it's not important
I'm guessing we can safely assume that this announcement means they've reached 85%... 😜 PW
 

ipdev

Recognized Contributor
Feb 14, 2016
1,924
1
3,541
Google Nexus 10
Nexus 7 (2013)
This is still intriguing me... I see this is OnePlus 7T, and it happens on rebooting...

Just wondering if you have ever patched / flashed recovery image on this device?... Or is device swapping between A/B system slots somehow? (Do you have working systems on both?... Perhaps Magisk in boot_a and boot_b?)... PW
I am just confused. 🙃
More "What The ???"​
___

It kind of works now, but I have to choose if I want Zygisk on (=No Mobile Network) or Zygisk off (=Older version of Magisk).
I did flash the recovery image to get Magisk onto the device to begin with, everything else is "direct install (recommended)".
No A/B stuff..
- Did you patch the recovery image with Magisk.
- Replace the recovery image with the Magisk patched version and boot into system from Recovery
or..
Did you you use recovery to install Magisk (patch the boot image)?

I have only had a 7T for a few weeks.
Since OnePlus has switched their release/updates to OTA only, it took me a little while to find a boot image.
Once I found it, I patched it with Magisk and ...​

Currently my (new-to-me) 7T is on the a12 beta.
I was testing the fingerprint scanner.​

I was planning on restoring to stable/stock OOS this weekend.
If you are running a custom ROM or kernel, let me know.
I am willing to test. 🙂
___

Very interesting...

So can I assume 7T has recovery_a/_b partitions as I believe 8T does, and that you also patched either recovery_a or _b in Magisk App some time back?

If this is correct, I'm guessing Zygisk-off somehow causes device to reboot to system via recovery, and you thus have old Magisk since you patched recovery image (which is also a boot image containing ramdisk of course) with that some time ago...

Note: Magisk in recovery and customised protocol for reboot via recovery to system w/o special adapted recovery key combo was designed for A-only legacy SAR devices specifically as these require Magisk in recovery partition as they have no ramdisk in boot... You seem to have used it on your 2SI device and there is no reason it shouldn't work apart from the fact that Magisk in boot partion is far more desirable / convenient...

If I'm correct about a/b partitioning in 7T, your modern 2SI boot type device will of course have ramdisk in 4 partitions, recovery_a and _b, also boot_a and _b... This is fairly unique as most 2SI devices use recovery in boot partition (w/ a hybrid ramdisk) and have no actual recovery partitions.

Again, if I'm right you can test theory by booting from powered down state using recovery key combo with this adjustment: As soon as you press the key combo and the device vibrates with a splash screen, release all buttons to boot into Magisk. (If you wanted to boot into the actual recovery mode, you would long press volume up until you see the recovery screen.)
https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery

Please reply to confirm (or correct) this! 😛 PW

OnePlus 7T partitions.
Code:
OnePlus7T:/ # ls -la dev/block/by-name/
total 0
drwxr-xr-x 2 root root 2520 1972-09-19 21:06 .
drwxr-xr-x 6 root root 4280 1972-09-19 21:06 ..
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 ALIGN_TO_128K_1 -> /dev/block/sdd1
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 ALIGN_TO_128K_2 -> /dev/block/sdf1
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 LOGO_a -> /dev/block/sde21
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 LOGO_b -> /dev/block/sde47
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 abl_a -> /dev/block/sde8
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 abl_b -> /dev/block/sde35
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 aging -> /dev/block/sde54
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 aging_mod -> /dev/block/sde55
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 aop_a -> /dev/block/sde1
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 aop_b -> /dev/block/sde28
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 apdp -> /dev/block/sde59
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 bluetooth_a -> /dev/block/sde5
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 bluetooth_b -> /dev/block/sde32
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 boot_a -> /dev/block/sde11
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 boot_b -> /dev/block/sde38
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 carrier -> /dev/block/sda15
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 catecontentfv -> /dev/block/sde72
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 catefv -> /dev/block/sde71
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 cateloader -> /dev/block/sde66
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 cdt -> /dev/block/sdd2
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 cmnlib64_a -> /dev/block/sde13
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 cmnlib64_b -> /dev/block/sde40
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 cmnlib_a -> /dev/block/sde12
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 cmnlib_b -> /dev/block/sde39
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 config -> /dev/block/sda12
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 core_nhlos -> /dev/block/sde20
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 ddr -> /dev/block/sdd3
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 devcfg_a -> /dev/block/sde14
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 devcfg_b -> /dev/block/sde41
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 devinfo -> /dev/block/sde57
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 dip -> /dev/block/sde58
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 dsp_a -> /dev/block/sde9
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 dsp_b -> /dev/block/sde36
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 dtbo_a -> /dev/block/sde17
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 dtbo_b -> /dev/block/sde44
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 frp -> /dev/block/sda6
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 fsc -> /dev/block/sdf5
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 fsg -> /dev/block/sdf4
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs1_a -> /dev/block/sde22
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs1_b -> /dev/block/sde48
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs2_a -> /dev/block/sde23
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs2_b -> /dev/block/sde49
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs3_a -> /dev/block/sde24
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs3_b -> /dev/block/sde50
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs4_a -> /dev/block/sde25
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs4_b -> /dev/block/sde51
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs5_a -> /dev/block/sde26
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs5_b -> /dev/block/sde52
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 hyp_a -> /dev/block/sde3
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 hyp_b -> /dev/block/sde30
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 imagefv_a -> /dev/block/sde19
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 imagefv_b -> /dev/block/sde46
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 keymaster_a -> /dev/block/sde10
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 keymaster_b -> /dev/block/sde37
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 keystore -> /dev/block/sda5
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 limits -> /dev/block/sde63
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 logdump -> /dev/block/sde67
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 logfs -> /dev/block/sde65
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdm1m9kefs1 -> /dev/block/sdf7
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdm1m9kefs2 -> /dev/block/sdf8
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdm1m9kefs3 -> /dev/block/sdf6
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdm1m9kefsc -> /dev/block/sdf9
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 mdm1oemnvbktmp -> /dev/block/sde77
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 mdm_oem_dycnvbk -> /dev/block/sda10
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 mdm_oem_stanvbk -> /dev/block/sda11
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdmddr -> /dev/block/sdd4
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdtp_a -> /dev/block/sde7
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 mdtp_b -> /dev/block/sde34
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdtpsecapp_a -> /dev/block/sde6
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 mdtpsecapp_b -> /dev/block/sde33
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 metadata -> /dev/block/sda21
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 misc -> /dev/block/sda3
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 modem_a -> /dev/block/sde4
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 modem_b -> /dev/block/sde31
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 modemst1 -> /dev/block/sdf2
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 modemst2 -> /dev/block/sdf3
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 msadp -> /dev/block/sde60
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 multiimgoem_a -> /dev/block/sde27
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 multiimgoem_b -> /dev/block/sde53
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 oem_dycnvbk -> /dev/block/sda8
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 oem_stanvbk -> /dev/block/sda9
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 op1 -> /dev/block/sde56
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 op2 -> /dev/block/sda7
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 opproduct_a -> /dev/block/sda13
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 opproduct_b -> /dev/block/sda14
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 param -> /dev/block/sda4
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 persist -> /dev/block/sda2
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 qupfw_a -> /dev/block/sde15
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 qupfw_b -> /dev/block/sde42
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 rawdump -> /dev/block/sda22
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 recovery_a -> /dev/block/sda17
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 recovery_b -> /dev/block/sda18
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 reserve1 -> /dev/block/sde73
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 reserve2 -> /dev/block/sde74
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 reserve3 -> /dev/block/sde75
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 reserve4 -> /dev/block/sde76
lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sda -> /dev/block/sda
lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sdb -> /dev/block/sdb
lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sdc -> /dev/block/sdc
lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sdd -> /dev/block/sdd
lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sde -> /dev/block/sde
lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sdf -> /dev/block/sdf
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 secdata -> /dev/block/sde70
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 splash -> /dev/block/sde62
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 spunvm -> /dev/block/sde61
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 ssd -> /dev/block/sda1
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 storsec_a -> /dev/block/sde68
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 storsec_b -> /dev/block/sde78
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 super -> /dev/block/sda16
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 toolsfv -> /dev/block/sde64
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 tz_a -> /dev/block/sde2
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 tz_b -> /dev/block/sde29
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 uefisecapp_a -> /dev/block/sde18
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 uefisecapp_b -> /dev/block/sde45
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 uefivarstore -> /dev/block/sde69
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 userdata -> /dev/block/sda23
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 vbmeta_a -> /dev/block/sde16
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 vbmeta_b -> /dev/block/sde43
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 vbmeta_system_a -> /dev/block/sda19
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 vbmeta_system_b -> /dev/block/sda20
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 xbl_a -> /dev/block/sdb1
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 xbl_b -> /dev/block/sdc1
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 xbl_config_a -> /dev/block/sdb2
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 xbl_config_b -> /dev/block/sdc2
OnePlus7T:/ #

Cheers. :cowboy:
 
  • Like
Reactions: galaxys and pndwal

pndwal

Senior Member
As always, Mad donno
(Edit: Offending remark has been removed by a moderator...)

Why do you continue this theme... I never read where John Wu said it either; just hearsay...

I don't need to keep hearing such remarks about anyone helping with Magisk etc, but confess I prefer polite company... And this is impolite (at best) at least among English speakers... 🙄 PW
 
Last edited:

pndwal

Senior Member
I am just confused. 🙃
More "What The ???"​
___


- Did you patch the recovery image with Magisk.
- Replace the recovery image with the Magisk patched version and boot into system from Recovery
or..
Did you you use recovery to install Magisk (patch the boot image)?

I have only had a 7T for a few weeks.
Since OnePlus has switched their release/updates to OTA only, it took me a little while to find a boot image.​
Once I found it, I patched it with Magisk and ...​

Currently my (new-to-me) 7T is on the a12 beta.
I was testing the fingerprint scanner.​

I was planning on restoring to stable/stock OOS this weekend.
If you are running a custom ROM or kernel, let me know.
I am willing to test. 🙂
___



OnePlus 7T partitions.
Code:
OnePlus7T:/ # ls -la dev/block/by-name/
total 0
drwxr-xr-x 2 root root 2520 1972-09-19 21:06 .
drwxr-xr-x 6 root root 4280 1972-09-19 21:06 ..
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 ALIGN_TO_128K_1 -> /dev/block/sdd1
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 ALIGN_TO_128K_2 -> /dev/block/sdf1
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 LOGO_a -> /dev/block/sde21
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 LOGO_b -> /dev/block/sde47
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 abl_a -> /dev/block/sde8
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 abl_b -> /dev/block/sde35
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 aging -> /dev/block/sde54
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 aging_mod -> /dev/block/sde55
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 aop_a -> /dev/block/sde1
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 aop_b -> /dev/block/sde28
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 apdp -> /dev/block/sde59
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 bluetooth_a -> /dev/block/sde5
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 bluetooth_b -> /dev/block/sde32
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 boot_a -> /dev/block/sde11
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 boot_b -> /dev/block/sde38
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 carrier -> /dev/block/sda15
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 catecontentfv -> /dev/block/sde72
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 catefv -> /dev/block/sde71
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 cateloader -> /dev/block/sde66
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 cdt -> /dev/block/sdd2
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 cmnlib64_a -> /dev/block/sde13
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 cmnlib64_b -> /dev/block/sde40
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 cmnlib_a -> /dev/block/sde12
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 cmnlib_b -> /dev/block/sde39
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 config -> /dev/block/sda12
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 core_nhlos -> /dev/block/sde20
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 ddr -> /dev/block/sdd3
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 devcfg_a -> /dev/block/sde14
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 devcfg_b -> /dev/block/sde41
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 devinfo -> /dev/block/sde57
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 dip -> /dev/block/sde58
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 dsp_a -> /dev/block/sde9
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 dsp_b -> /dev/block/sde36
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 dtbo_a -> /dev/block/sde17
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 dtbo_b -> /dev/block/sde44
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 frp -> /dev/block/sda6
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 fsc -> /dev/block/sdf5
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 fsg -> /dev/block/sdf4
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs1_a -> /dev/block/sde22
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs1_b -> /dev/block/sde48
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs2_a -> /dev/block/sde23
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs2_b -> /dev/block/sde49
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs3_a -> /dev/block/sde24
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs3_b -> /dev/block/sde50
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs4_a -> /dev/block/sde25
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs4_b -> /dev/block/sde51
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs5_a -> /dev/block/sde26
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs5_b -> /dev/block/sde52
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 hyp_a -> /dev/block/sde3
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 hyp_b -> /dev/block/sde30
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 imagefv_a -> /dev/block/sde19
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 imagefv_b -> /dev/block/sde46
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 keymaster_a -> /dev/block/sde10
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 keymaster_b -> /dev/block/sde37
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 keystore -> /dev/block/sda5
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 limits -> /dev/block/sde63
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 logdump -> /dev/block/sde67
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 logfs -> /dev/block/sde65
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdm1m9kefs1 -> /dev/block/sdf7
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdm1m9kefs2 -> /dev/block/sdf8
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdm1m9kefs3 -> /dev/block/sdf6
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdm1m9kefsc -> /dev/block/sdf9
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 mdm1oemnvbktmp -> /dev/block/sde77
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 mdm_oem_dycnvbk -> /dev/block/sda10
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 mdm_oem_stanvbk -> /dev/block/sda11
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdmddr -> /dev/block/sdd4
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdtp_a -> /dev/block/sde7
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 mdtp_b -> /dev/block/sde34
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdtpsecapp_a -> /dev/block/sde6
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 mdtpsecapp_b -> /dev/block/sde33
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 metadata -> /dev/block/sda21
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 misc -> /dev/block/sda3
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 modem_a -> /dev/block/sde4
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 modem_b -> /dev/block/sde31
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 modemst1 -> /dev/block/sdf2
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 modemst2 -> /dev/block/sdf3
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 msadp -> /dev/block/sde60
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 multiimgoem_a -> /dev/block/sde27
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 multiimgoem_b -> /dev/block/sde53
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 oem_dycnvbk -> /dev/block/sda8
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 oem_stanvbk -> /dev/block/sda9
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 op1 -> /dev/block/sde56
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 op2 -> /dev/block/sda7
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 opproduct_a -> /dev/block/sda13
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 opproduct_b -> /dev/block/sda14
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 param -> /dev/block/sda4
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 persist -> /dev/block/sda2
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 qupfw_a -> /dev/block/sde15
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 qupfw_b -> /dev/block/sde42
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 rawdump -> /dev/block/sda22
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 recovery_a -> /dev/block/sda17
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 recovery_b -> /dev/block/sda18
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 reserve1 -> /dev/block/sde73
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 reserve2 -> /dev/block/sde74
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 reserve3 -> /dev/block/sde75
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 reserve4 -> /dev/block/sde76
lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sda -> /dev/block/sda
lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sdb -> /dev/block/sdb
lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sdc -> /dev/block/sdc
lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sdd -> /dev/block/sdd
lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sde -> /dev/block/sde
lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sdf -> /dev/block/sdf
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 secdata -> /dev/block/sde70
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 splash -> /dev/block/sde62
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 spunvm -> /dev/block/sde61
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 ssd -> /dev/block/sda1
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 storsec_a -> /dev/block/sde68
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 storsec_b -> /dev/block/sde78
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 super -> /dev/block/sda16
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 toolsfv -> /dev/block/sde64
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 tz_a -> /dev/block/sde2
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 tz_b -> /dev/block/sde29
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 uefisecapp_a -> /dev/block/sde18
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 uefisecapp_b -> /dev/block/sde45
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 uefivarstore -> /dev/block/sde69
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 userdata -> /dev/block/sda23
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 vbmeta_a -> /dev/block/sde16
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 vbmeta_b -> /dev/block/sde43
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 vbmeta_system_a -> /dev/block/sda19
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 vbmeta_system_b -> /dev/block/sda20
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 xbl_a -> /dev/block/sdb1
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 xbl_b -> /dev/block/sdc1
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 xbl_config_a -> /dev/block/sdb2
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 xbl_config_b -> /dev/block/sdc2
OnePlus7T:/ #

Cheers. :cowboy:
Thanks for that... Confims that I just might be on the money... 😅 PW
 
  • Like
Reactions: galaxys and ipdev

Stillhard

Senior Member
Sep 25, 2016
152
124
Why do you continue this theme... I never read where John Wu said it either; just hearsay...

I don't need to keep hearing such remarks about anyone helping with Magisk etc, but confess I prefer polite company... And this is impolite (at best) at least among English speakers... 🙄 PW
I don't know why i can't?
You brought it here in Official - Magisk General Support Discussion, you could just bring it in it's own thread, but you can, so why i can't?
 

pndwal

Senior Member
I don't know why i can't?
You brought it here in Official - Magisk General Support Discussion, you could just bring it in it's own thread, but you can, so why i can't?
I did not.

I have never furthered this
As always, Mad donno
(Edit: Offending remark has been removed by a moderator...)

theme here, nor have I been one to take it to any other thread... And, to be quite clear, I'm referring to your self evident sexual suggestions, not some unstated link to things Alpha or any other Magisk related issues...

Sorry to spell it out, but you haven't gotten the (none too subtle) hint! 😜😛 PW
 
Last edited:
  • Haha
Reactions: Stillhard

maakosan

Member
Aug 24, 2012
39
6
Brisbane
I am just confused. 🙃
More "What The ???"​
___


- Did you patch the recovery image with Magisk.
- Replace the recovery image with the Magisk patched version and boot into system from Recovery
or..
Did you you use recovery to install Magisk (patch the boot image)?

I have only had a 7T for a few weeks.
Since OnePlus has switched their release/updates to OTA only, it took me a little while to find a boot image.​
Once I found it, I patched it with Magisk and ...​

Currently my (new-to-me) 7T is on the a12 beta.
I was testing the fingerprint scanner.​

I was planning on restoring to stable/stock OOS this weekend.
If you are running a custom ROM or kernel, let me know.
I am willing to test. 🙂
___



OnePlus 7T partitions.
Code:
OnePlus7T:/ # ls -la dev/block/by-name/
total 0
drwxr-xr-x 2 root root 2520 1972-09-19 21:06 .
drwxr-xr-x 6 root root 4280 1972-09-19 21:06 ..
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 ALIGN_TO_128K_1 -> /dev/block/sdd1
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 ALIGN_TO_128K_2 -> /dev/block/sdf1
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 LOGO_a -> /dev/block/sde21
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 LOGO_b -> /dev/block/sde47
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 abl_a -> /dev/block/sde8
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 abl_b -> /dev/block/sde35
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 aging -> /dev/block/sde54
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 aging_mod -> /dev/block/sde55
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 aop_a -> /dev/block/sde1
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 aop_b -> /dev/block/sde28
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 apdp -> /dev/block/sde59
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 bluetooth_a -> /dev/block/sde5
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 bluetooth_b -> /dev/block/sde32
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 boot_a -> /dev/block/sde11
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 boot_b -> /dev/block/sde38
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 carrier -> /dev/block/sda15
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 catecontentfv -> /dev/block/sde72
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 catefv -> /dev/block/sde71
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 cateloader -> /dev/block/sde66
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 cdt -> /dev/block/sdd2
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 cmnlib64_a -> /dev/block/sde13
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 cmnlib64_b -> /dev/block/sde40
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 cmnlib_a -> /dev/block/sde12
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 cmnlib_b -> /dev/block/sde39
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 config -> /dev/block/sda12
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 core_nhlos -> /dev/block/sde20
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 ddr -> /dev/block/sdd3
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 devcfg_a -> /dev/block/sde14
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 devcfg_b -> /dev/block/sde41
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 devinfo -> /dev/block/sde57
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 dip -> /dev/block/sde58
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 dsp_a -> /dev/block/sde9
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 dsp_b -> /dev/block/sde36
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 dtbo_a -> /dev/block/sde17
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 dtbo_b -> /dev/block/sde44
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 frp -> /dev/block/sda6
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 fsc -> /dev/block/sdf5
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 fsg -> /dev/block/sdf4
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs1_a -> /dev/block/sde22
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs1_b -> /dev/block/sde48
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs2_a -> /dev/block/sde23
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs2_b -> /dev/block/sde49
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs3_a -> /dev/block/sde24
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs3_b -> /dev/block/sde50
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs4_a -> /dev/block/sde25
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs4_b -> /dev/block/sde51
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs5_a -> /dev/block/sde26
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs5_b -> /dev/block/sde52
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 hyp_a -> /dev/block/sde3
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 hyp_b -> /dev/block/sde30
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 imagefv_a -> /dev/block/sde19
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 imagefv_b -> /dev/block/sde46
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 keymaster_a -> /dev/block/sde10
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 keymaster_b -> /dev/block/sde37
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 keystore -> /dev/block/sda5
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 limits -> /dev/block/sde63
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 logdump -> /dev/block/sde67
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 logfs -> /dev/block/sde65
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdm1m9kefs1 -> /dev/block/sdf7
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdm1m9kefs2 -> /dev/block/sdf8
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdm1m9kefs3 -> /dev/block/sdf6
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdm1m9kefsc -> /dev/block/sdf9
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 mdm1oemnvbktmp -> /dev/block/sde77
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 mdm_oem_dycnvbk -> /dev/block/sda10
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 mdm_oem_stanvbk -> /dev/block/sda11
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdmddr -> /dev/block/sdd4
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdtp_a -> /dev/block/sde7
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 mdtp_b -> /dev/block/sde34
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdtpsecapp_a -> /dev/block/sde6
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 mdtpsecapp_b -> /dev/block/sde33
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 metadata -> /dev/block/sda21
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 misc -> /dev/block/sda3
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 modem_a -> /dev/block/sde4
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 modem_b -> /dev/block/sde31
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 modemst1 -> /dev/block/sdf2
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 modemst2 -> /dev/block/sdf3
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 msadp -> /dev/block/sde60
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 multiimgoem_a -> /dev/block/sde27
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 multiimgoem_b -> /dev/block/sde53
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 oem_dycnvbk -> /dev/block/sda8
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 oem_stanvbk -> /dev/block/sda9
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 op1 -> /dev/block/sde56
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 op2 -> /dev/block/sda7
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 opproduct_a -> /dev/block/sda13
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 opproduct_b -> /dev/block/sda14
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 param -> /dev/block/sda4
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 persist -> /dev/block/sda2
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 qupfw_a -> /dev/block/sde15
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 qupfw_b -> /dev/block/sde42
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 rawdump -> /dev/block/sda22
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 recovery_a -> /dev/block/sda17
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 recovery_b -> /dev/block/sda18
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 reserve1 -> /dev/block/sde73
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 reserve2 -> /dev/block/sde74
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 reserve3 -> /dev/block/sde75
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 reserve4 -> /dev/block/sde76
lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sda -> /dev/block/sda
lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sdb -> /dev/block/sdb
lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sdc -> /dev/block/sdc
lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sdd -> /dev/block/sdd
lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sde -> /dev/block/sde
lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sdf -> /dev/block/sdf
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 secdata -> /dev/block/sde70
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 splash -> /dev/block/sde62
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 spunvm -> /dev/block/sde61
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 ssd -> /dev/block/sda1
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 storsec_a -> /dev/block/sde68
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 storsec_b -> /dev/block/sde78
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 super -> /dev/block/sda16
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 toolsfv -> /dev/block/sde64
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 tz_a -> /dev/block/sde2
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 tz_b -> /dev/block/sde29
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 uefisecapp_a -> /dev/block/sde18
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 uefisecapp_b -> /dev/block/sde45
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 uefivarstore -> /dev/block/sde69
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 userdata -> /dev/block/sda23
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 vbmeta_a -> /dev/block/sde16
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 vbmeta_b -> /dev/block/sde43
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 vbmeta_system_a -> /dev/block/sda19
lrwxrwxrwx 1 root root   16 1972-09-19 21:06 vbmeta_system_b -> /dev/block/sda20
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 xbl_a -> /dev/block/sdb1
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 xbl_b -> /dev/block/sdc1
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 xbl_config_a -> /dev/block/sdb2
lrwxrwxrwx 1 root root   15 1972-09-19 21:06 xbl_config_b -> /dev/block/sdc2
OnePlus7T:/ #

Cheers. :cowboy:
The first thing you said..
Did you patch the recovery image with Magisk.
- Replace the recovery image with the Magisk patched version and boot into system from Recovery
 

Tech = Spy-Biz

Account currently disabled
May 25, 2022
32
20
TJW did a great job, I can't possibly read 2648 pages of this thread, I have used older magisk versions before but now with 24.2 loaded the bank apps detect root. I'm using samsung device with android 11, I've enabled zygisk , changed the magisk app name, added all the bank app processes to denylist, rebooted. My ROM shows Software Status: Official even though bootloader unlocked & twrp installed. Can anyone tell me which exact version of magisk might hide root from bank apps? TIA
 

meric57

Senior Member
Oct 2, 2017
223
39
Oeutrange
Samsung Galaxy Tab E
Hello, I agree with Tech = Spy-Biz I propose that each concern be listed in an ad as a pos-it.
Example concern with bank metering the solution concern for updating metering the solution thus immediately, it will avoid overwork to seek the solution in 2648 pages
I'm off topic these for ease and avoid searches
 
  • Like
Reactions: Tech = Spy-Biz

zgfg

Senior Member
Oct 10, 2016
7,814
5,226
By the way, there is another thread with detailed OP instructions for the new Magisk v24/v25:

And a thread that was opened for hiding root with the new Magisk:

Those new threads were opened because of this old and cluttered thread.
Unfortunately, people still report/ask here (and in parallel complain that thread is too big to read☹️)
 

pndwal

Senior Member
The first thing you said..
Did you patch the recovery image with Magisk.
- Replace the recovery image with the Magisk patched version and boot into system from Recovery
Thanks for that... Confims that I just might be am on the money!... 😂

To be honest, I've thought about running dual Magisk iterations this way, but yours is the first case I've seen... And you did it by accident! 😅 ... Well done...

Clearly you need to flash unpatched recovery again to remove (old) Magisk in recovery partition... This configuration was never meant for your device anyway...

So we just need to figure out issue with mobile network in Magisk (25.2) in boot partition to fully solve the puzzle...

I'd flash the stock recovery, then try reboots to see if Magisk 25.2 in boot partition is fixed (ie. Magisk with working Zygisk and mobile network)... Previously such reboots were apparently sabotaged by Magisk in recovery partition booting system with different root binaries...

I have my doubts that this will solve the network issue; I suspect you have also mixed up boot images and may have flashed a patched one from an earlier or different ROM (eg using the same image you had before taking an OTA update = mismatched boot image)... maybe you didn't download properly matching ROM (version must be a perfect match with running version as in Settings, About device).

Mismatched boot images are the most common cause of issues like yours w/ Magisk. These will often allow system to boot, but generally with comms (sim, wifi, bt) and many other issues...

Exact matches are needed because the kernel also resides in the boot image and this gets much attention from devs ... System changes often have corresponding changes in kernel (ie. in boot) with any OTA to accommodate many 'handshakes' made between system and kernel. See: https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-86520073

Anyway, fix your recovery partition(s) and try the reboots first... 🙂 PW
 
Last edited:
  • Like
Reactions: galaxys and ipdev

AndroLinx

Member
Mar 8, 2020
13
2
Hi there,

I would like to root a Galaxy Tab S6 lite Wifi running on LineageOS 19.1 using Magisk 25.2.
The installation instructions I found on rooting suggest to download and patch an original Samsung firmware.
Question is whether this really applies if one runs a custom rom like LineageOS or if I should rather patch the lineageOS boot.img?

Thanks in advance for any hints!
 
  • Like
Reactions: martyfender

Franzyy

Senior Member
I have a issue in magisk where i cant activate mobile data and make calls anymore, it also says no imei, please fix it in the next update. I use the A32 (a325f) where i flashed magisk through boot.img
More about this here:
 

zgfg

Senior Member
Oct 10, 2016
7,814
5,226
I have a issue in magisk where i cant activate mobile data and make calls anymore, it also says no imei, please fix it in the next update. I use the A32 (a325f) where i flashed magisk through boot.img
More about this here:
Who will fix it?!

Developer(s) don't read this thread

To report issues, you need to go to Magisk GitHub 🤣
 

pndwal

Senior Member
I have a issue in magisk where i cant activate mobile data and make calls anymore, it also says no imei, please fix it in the next update. I use the A32 (a325f) where i flashed magisk through boot.img
More about this here:
So this known stale issue?:
https://github.com/topjohnwu/Magisk/issues/1801
Thank you so much, my A32 has mobile data again.
I guess you found workaround(s) linked from that issue...

Assuming you are trying w/ latest Magisk it seems you need that for now... PW
 

Top Liked Posts

  • 3
    Yeah, even better and more friendly

    I think safe mode using key combination is not very reliable, or at best requires a tricky timing.
    @gecowa6967 can comment, but it wouldn't work for him, not sure if it booted to safe mode and Magisk failed to disable the modules (in which case it would be a Magisk bug) or Safe mode never got activated.

    I personally didn't know that we could boot to safe mode from the UI, which was a great tip that we can try if this happens again, I know that gecowa6967 was not the only one that experienced this issue.

    Yes, I was not able to boot into safe mode using key combination when I was using the patched boot image.

    I only have the log of the bootloop I posted before, I do not know which module caused the issue. Once I was able to boot with my modified patched boot image, I ran "magisk --remove-modules" to remove all modules.

    When I ran "magisk --remove-modules" with the "normally" patched boot image during boot, the phone would restart, but the modules would not be removed. I think magisk did not have write permission for the folder or something like this.

    The idea of a "dumb" patched image that does not load any modules would have been good, that's why I posted the APK for anyone else having this issue.

    I am very grateful for all the kind feedback you gave me for my hacky solution. And also thank you to my roommate who helped me with all of this. :)
    2
    .....the only catch with MBP is that users need to have had that module prior to the problem.... this being integrated into Magisk makes it simpler and easier.
    Screenshot_20221004_130934.jpg
    1
    We can't write to /data/adb/modules without root (and we're bootlooping with root), hence why it has to be to somewhere like /data/local/tmp
    We definitely can create such file in adb which would have helped @gecowa6967
    Yup, but doesn't this still require USB debugging enabled?... And @gecowa6967 had issue where adb command magisk --remove-modules had no effect...
    but can we create such file using fastboot?

    I looked at fastboot commands, and I see this, but I have no idea how to use it and if it can help us create an empty file
    Code:
    Android Things:
     stage IN_FILE              Sends given file to stage for the next command.
     get_staged OUT_FILE        Writes data staged by the last command to a file.

    If we can, then @gecowa6967 code, instead of disabling loading modules would simply look for the presence of such file and if found skip loading the modules.
    Yup... No idea either. 😶
    I don't see that Fastboot is needed
    It's just a working possibly (actually allowed the fix used); seems ADB (requires USB debugging enabled anyway) and Safemode (user could only enter it w/ unpatched boot image) had no effect and are also often inaccessible to other users...
    ...Even more user friendly: let it be a file on Internal memory (like in Download folder) - hence one does not even need to pinpoint with adb

    For this, root is not needed and without Magisk, there should be no bootloop due to the modules

    3) Then flash back the patched boot.img and reboot.
    Magisk should read the file from step 2 and disable the module(s)
    This seems a good approach...

    My further thoughts: Seems it would be even simpler to restore old core-only mode toggle in-app instead of using a file-based flag however...

    Of course we could then simply flash unpatched image and set this mode in such an 'emergency' before re-flashing patched image to boot Magisk w/ modules disabled! 🤪

    This would also circumvent these difficulties:
    - Magisk uses /data/adb (not /data/local/tmp or Internal memory) since an app needs a root to access there.
    Otherwise, all banking and similar apps would be able to read...

    Magisk might even delete that file once it consumes the command...
    -----​
    I think safe mode using key combination is not very reliable, or at best requires a tricky timing.
    Correct...
    @gecowa6967 can comment, but it wouldn't work for him, not sure if it booted to safe mode and Magisk failed to disable the modules (in which case it would be a Magisk bug) or Safe mode never got activated.
    He was only able to boot to Android Safe mode w/o root (ie after flashing unpatched boot image) which doesn't trip Magisk Safe mode (requires running Magisk daemon to detect Safe mode triggers and to set flags for disabling modules)... Not a Magisk bug since it wasn't running! 😉
    I personally didn't know that we could boot to safe mode from the UI, which was a great tip that we can try if this happens again, I know that gecowa6967 was not the only one that experienced this issue.
    And need for running Magisk daemon is the key to this too; We boot to Android Safe mode w/o root but rely on reboot after a fastboot flash (we access fastboot from Safe mode to flash Magisk-patched image) being reboot back to Safe Mode... Modules will only be disabled at this point...
    Although I still don't understand what is wrong with Safe Mode. Are there devices that cannot boot to Android Safe Mode, or just ppl don't know about, or don't know (google about) how to use the fingers to boot to the Safe mode
    User simply couldn't get access w/ key combo w/ patched boot image, but this is also problematic due to Magisk's need to detect user entering key combo (booting from off state only) and timing is also critical... Eg on MIUI we can generally get Android Safe Mode w/o triggering Magisk Safe Mode unless we alter the usually key release timing... I know others have also had different problems with this approach...
    In fact, nost of the stuff above (a control file on /data/local/tmp and so) makes actually a re-inventiion of the wheel...
    Praps we could just use an old wheel (Core Only mode) again for emergency use!... 😋 PW
    1
    ... one more good feature in the latest Delta - Clean Hidelist...
  • 7
    Can someone either provide actual proof that zygisk/shamiko etc does anything to GPS (i havent had a single issue and i use it daily) or i dunno, maybe stop spreading FUD because of personal gripes you have against people on other platforms that dont take part here, and therefore wont get any of the swipes youre taking at them here that only further add to the aforementioned FUD.

    We've all had our moments with those folk and its fine to mention the odd bit of spice you may come across when trying to submit an issue on github (ive done this myself), but to then to continually poison magisk proper/shamiko because of that person/persons taking part is not helping anyone. Thats a personal gripe, and shouldnt colour the entire magisk (proper) project/shamiko. What we dont need is spice here....

    Please, you know who you are...

    I think we've all had enough, now
    5
    I'm using the systemless debloater module to degoogle and debloat a device (and several other magisk modules to assist in that endeavor). I'd really like to be able to do a factory reset to clear the device of any data/artifacts from the debloated apps, but of course a factory reset wipes out magisk modules, so I'm in a catch 22.
    You can do some cleaning like this:

    - Wipe (from TWRP or by root explorer like MiXPlorer)
    /data/dalwik-cache
    /data/system/package_cache

    -In MiXPlorer, go to three dots, Tools and clean by App Remnants

    -Install SD Maid:
    And clean by CorpsFinder option
    5
    Installing on Samsung S7 (SM-G930F) with /e/OS?
    Okay folks, thought I'd post up the procedure:
    1. Follow these instructions until you get to 7th bullet point here;
    2. Stop. Some points to mention on the way:
      1. Note my progress above from 'Preliminaries' until point 5, adb pull /sdcard/Download/magisk_patched_[random_strings].img works just fine;
      2. Ignore my rambling queries up to point 5;
    3. Install heimdall;
    4. Boot device into 'Download' mode without USB cable connected, then once in 'Download' mode insert USB cable (this seemed important as I ran into quite a lot of ERROR: Protocol initialisation failed! type errors which seemed possibly cable/ hardware related);
    5. Bash:
      $ heimdall detect
      Device detected
      $ heimdall print-pit --no-reboot > print-pit.txt
    6. From print-pit.txt discover:
      ...
      --- Entry #10 ---
      Binary Type: 0 (AP)
      Device Type: 8 (Unknown)
      Identifier: 5
      Attributes: 5 (Read/Write)
      Update Attributes: 1 (FOTA)
      Partition Block Size/Offset: 10240
      Partition Block Count: 10240
      File Offset (Obsolete): 0
      File Size (Obsolete): 0
      Partition Name: BOOT
      Flash Filename: boot.img
      FOTA Filename:
      ...
    7. Reboot into 'Download' mode (this rebooting also seemed to help prevent the above errors);
    8. Bash:
      $ heimdall detect
      Device detected
      $
    9. Then, instead of fastboot flash boot /path/to/magisk_patched.img at the 7th bullet point here
      Do:

      Bash:
      $ heimdall flash --BOOT magisk_patched-25200_UjUVt.img
      Heimdall v1.4.2
      
      Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
      http://www.glassechidna.com.au/
      
      This software is provided free of charge. Copying and redistribution is
      encouraged.
      
      If you appreciate this software and you would like to support future
      development please consider donating:
      http://www.glassechidna.com.au/donate/
      
      Initialising connection...
      Detecting device...
      Claiming interface...
      Setting up interface...
      
      Initialising protocol...
      Protocol initialisation successful.
      
      Beginning session...
      
      Some devices may take up to 2 minutes to respond.
      Please be patient!
      
      Session begun.
      
      Downloading device's PIT file...
      PIT file download successful.
      
      Uploading BOOT
      100%
      BOOT upload successful
      
      Ending session...
      Rebooting device...
      Releasing device interface...
      
      $
    10. At which, the device reboots and:
      Screenshot_20220927-133842_Magisk.png
    11. Happiness :)
    5
    How does PixelFlasher invoke boot_patch.sh?
    Does it invoke it as an "executable", creating a new process? Or does it "source" it, so changes to the environment will survive?

    Does PixelFlasher create an environment variable named "SHA1"?

    My copy of boot_patch.sh has a compound statement that tests whether SHA1 has a non-zero length value before setting it to the sha1 of the boot image. If the environment variable is already set, it will not be overwritten. I don't know why.
    I wouldn't source. The script is supposed to be called as an executable

    Eg, my following code is rather primitive but it dumps the active Boot partition (it supports A/B and non-A/B devices), then it patches by invoking the boot_patch.sh script, finally it dumps back to the Boot partition and automatically reboots

    Ie, it updates me the Magisk and it also leaves me the patched-boot img in the Download folder

    Code:
    #!/system/bin/sh
    
    # Boot partition
    AB=$(getprop ro.boot.slot_suffix)
    BOOT_PART=/dev/block/bootdevice/by-name/boot"$AB"
    
    # Boot and patched boot images
    DOWNLOAD=/sdcard/Download/
    BOOT_IMG="$DOWNLOAD"boot.img
    PATCHED_BOOT_IMG="$DOWNLOAD"patched-boot.img
    
    # Magisk path
    MAGISK_PATH=/data/adb/magisk/
    
    # Disk-dump boot image to Download folder
    dd if="$BOOT_PART" of="$BOOT_IMG"
    
    # Patch the boot image and move to Download folder
    "$MAGISK_PATH"boot_patch.sh "$BOOT_IMG"
    mv "$MAGISK_PATH"new-boot.img "$PATCHED_BOOT_IMG"
    
    # Flash the patched boot image
    dd if="$PATCHED_BOOT_IMG" of="$BOOT_PART"
    
    # Reboot
    reboot
  • 1085
    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
    156
    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!!
    121
    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.
    75
    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