Magisk: [21.0] Magisk, "installed: N/A" through a patched boot.img
- Got the new Magisk Manager (8.0.0), made it Beta branch (because by default it still says Manager 7.5.1 and Magisk 20.4 are latest)
- Clicked "Install", Selected my (stock) rom's boot.img for patching.
- Copied magisk_patched.img (which was around 65mb compared to the ~10mb it was with 20.4 btw) to desktop
- Rebooted to fastboot mode and:
- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- fastboot erase cache
- fastboot flash boot magisk_patched.img
- fastboot reboot
Now Magisk Manager says Installed: N/A.
Not sure if it's the Manager not properly detecting that Magisk is present, or Magisk that isn't installed properly.
This installation method worked fine with 20.4
Phone: Redmi Note 9 (Merlin)
Android: 10
MIUI: 12.0.3
If you need anything else, let me know.
For now, I will roll back to the previous versions of both the Manager and Magisk itself.
Akitakek
All 40 comments
Same here.
I tried them both, Beta 302/21000 and Canary 303/21001. I flashed them with fastboot. No joy. Still Magisk Manager says N/A.
Phone: Oukitel WP5-PRO_EEA_V03_20200723
Baseband version: MOLY.LR12A.R3.MP.V114.9
kernel = 4.9.190+
Android 10
A/B = No
SAR = Yes
Ramdisk = Yes
I attached the log of the Canary installation and my zipped patched and unpatched boot.img
Alpamayo57
on 3 Oct 2020
Same here, but I'm using MIUI12 over Android 11. (K30 5G)
This phone has a snapdragon 765G.
Linux kernel 4.19.110
TooYoungTooSimp
on 3 Oct 2020
Are these A/B devices? If so I would argue Magisk isn't installed at all, I think something's broken with Magisk 21 and on A/B if one slot fails to boot it'll revert to the other slot. On my Pixel 4 XL attempting to flash Magisk 21 causes it to swap slots, and upon boot Magisk Manager reports N/A for me too.
ryaniskira
on 3 Oct 2020
From @abdoi94:
running canary
console-ramoops-0-magisk-21001-bootloop.txt
topjohnwu
on 3 Oct 2020
Are these A/B devices? If so I would argue Magisk isn't installed at all, I think something's broken with Magisk 21 and on A/B if one slot fails to boot it'll revert to the other slot. On my Pixel 4 XL attempting to flash Magisk 21 causes it to swap slots, and upon boot Magisk Manager reports N/A for me too.
Happens on MTK devices only, both my phone (redmi 9) and tablet (Fire HD 8) say magisk isn't installed after flashing a patched image, while my old HTC One M8 has no problems whatsoever. Noticed this on Canary but didn't have any time to report, I'm suspecting a recent commit but yet, I could be wrong
X1nto
on 4 Oct 2020
Happens on MTK devices only
According to @TooYoungTooSimp this happens on Qualcomm devices too.
kidonng
on 4 Oct 2020
Happens on MTK devices only
According to @TooYoungTooSimp this happens on Qualcomm devices too.
Oops, missed that
X1nto
on 4 Oct 2020
UPDATE: 21002 works for me.
I have the same setup with @TooYoungTooSimp's and failed to install v21 too.
- Mobile: Redmi K30 5G (Qualcomm 765G)
- ROM:
xiaomi.eu_multi_HMK305G_20.9.24_v12-11.zip(MIUI 12 / Android 11)
Some people who use Redmi K30 Pro (MIUI 12 / Android 11) reported that they are fine with v21 though.
jfcherng
on 4 Oct 2020
About the commit, I think it could indeed be the culprit. The magisk_patched.img is actually _larger_ than the stock boot.img, which could be causing issues if the partition it's flashed to isn't big enough?
Just speculation though.
Akitakek
on 4 Oct 2020
About the commit, I think it could indeed be the culprit. The magisk_patched.img is actually _larger_ than the stock boot.img, which could be causing issues if the partition it's flashed to isn't big enough?
Just speculation though.
Not sure about your device but with mine, patched image actually matched stock boot image size, the reason I think that commit is the issue, is because of how directly it's involved in the patched image output, if someone could get a canary build that doesn't contain that commit, we could test if that's the issue
X1nto
on 4 Oct 2020
@TooYoungTooSimp You may try canary 20423 (download: https://github.com/topjohnwu/magisk_files/raw/34fa199e57acaa99806b1353a351ef773b3249de/magisk-debug.zip) which works for my K30 5G (MIUI 12 / Android 11).
@X1nto @Akitakek Maybe you guys can give the above build a try?
UPDATE: sorry I failed to reproduce it :/ It just occasionally somehow worked once.
jfcherng
on 4 Oct 2020
Sounds like 2SI/SAR detection being finicky again, as with #2994
osm0sis
on 4 Oct 2020
Its been happening on My MTK A10 device since release. Tried each build from 17- 21 always shows not installed. And logcat has not a single line about magisk.init. Just couple lines about package manager and the magisk apk.
as to the size of the boot.img. My stock img is around 30md, and the patched img is close to 10mb. do not think oversized image is the issue
I do know that if I add prop files to stock boot.img, i can get adb root to function. Maybe this is interfering with magisk.
mrmazakblu
on 4 Oct 2020
I patched a boot.img, after trying to install, magisk prompts N/A。My device is Xiaomi 10 lite, Qualcomm 765G。Android 11/ MIUI12.This is the log of logcat dmesg, and the boot of the original factory boot and 21001/303magisk patch I used https://homekd.jerryliang.top/#s/6RqPwW1g
jerryliang122
on 5 Oct 2020
Same for Pixel 3a with a bootloop. It switches slots.
Edit: the Manager decided to patch the ramdisk with v20.4
jakiki6
on 5 Oct 2020
I tried updating from 20.4 to Magisk 21.0 and the latest Magisk Manager 8. 0.0 (302) (11). My phone is the Huawei Mate 9 with HiSilicon Kirin 960 chipset. My install also said N/A and appeared to not be rooted. Methods attempted in order:
1: Installed Magisk Manager 8.0.0 from within Magisk Manager. - Worked
2: Direct install method within Magisk Manager to 21.0. - Appeared successful but no root and given N/A for install status.
3: Zip install through TWRP. Install appeared successful but same results as above.
4: Zip install of the previous version 20.4 that I had installed while maintaining the new Manager version 8.0.0. - Successful and functionality is restored as before.
The new Magisk Manager is working fine. Magisk itself is not.
DrinkTaiTea
on 5 Oct 2020
another thing is that some user can't install magisk via twrp 'thanks to' dynamic partition. I have no twrp to use so I can only do a direct install.
TooYoungTooSimp
on 5 Oct 2020
another thing is that some user can't install magisk via twrp 'thanks to' dynamic partition. I have no twrp to use so I can only do a direct install.
This is why I use fastboot to flash magisk, supporting flashing via twrp is a pain in the ass
X1nto
on 5 Oct 2020
another thing is that some user can't install magisk via twrp 'thanks to' dynamic partition. I have no twrp to use so I can only do a direct install.
This is why I use fastboot to flash magisk, supporting flashing via twrp is a pain in the ass
patch boot image and flash it？ I believe it is the same as direct install. Or any other ways?
TooYoungTooSimp
on 5 Oct 2020
another thing is that some user can't install magisk via twrp 'thanks to' dynamic partition. I have no twrp to use so I can only do a direct install.
This is why I use fastboot to flash magisk, supporting flashing via twrp is a pain in the ass
patch boot image and flash it？ I believe it is the same as direct install. Or any other ways?
I believe it is the same as direct install. The difference is you can choose any boot image to patch, so it gives more leeway.
DrinkTaiTea
on 5 Oct 2020
I re-patched 20.4 without an issue (on the old manager), then updated to Manager 8.0.0, works fine.
Akitakek
on 6 Oct 2020
WE ARE NOT talking about direct install here, but about patching a boot.img and flashing it with fastboot.
Please stay on topic and create or add to the proper issue.
Akitakek
on 6 Oct 2020
WE ARE NOT talking about direct install here, but about patching a boot.img and flashing it with fastboot.
Please stay on topic and create or add to the proper issue.
Yes I know, but I have tried both methods here。PATCH and direct install.
jerryliang122
on 6 Oct 2020
Can people test out the latest canary build and see if it fixes the issue?
topjohnwu
on 8 Oct 2020
Already patching
X1nto
on 8 Oct 2020
Nope, still shows N/A on 04995881 build. I would get installation logs but I'm not sure how 😅
X1nto
on 8 Oct 2020
Nope, still shows N/A on 0499588 build. I would get installation logs but I'm not sure how 😅
It works on Qualcomm 765G (xiaomi 10 lite zoon)
jerryliang122
on 8 Oct 2020
Still not getting magisk init to start. On Either of my devices.
Both mtk, both released on A-10
logcat shows only references to 'magisk' are the apk and surfaceflinger.
logcat clips with grep "magisk" then grep "init"
https://del.dog/norylepanu
mrmazakblu
on 8 Oct 2020
Nope. It shows N/A on 0 4 9 9 5 8 8 1 (21002) (and MM d4d837a5 (308) )
Phone: Oukitel WP5-PRO_EEA_V03_20200723
Baseband version: MOLY.LR12A.R3.MP.V114.9
kernel = 4.9.190+
Android 10
A/B = No
SAR = Yes
Ramdisk = Yes
Alpamayo57
on 8 Oct 2020
Can people test out the latest canary build and see if it fixes the issue?
k30 5g （sd765g） 21002 fix confirmed. really thanks for your work.
TooYoungTooSimp
on 8 Oct 2020
21002 still goes stragiht to fastboot for me, tried patching image and flashing with twrp
abdoi94
on 8 Oct 2020
Canary build 04995881 (21002) now shows Magisk installed on my Pixel 3 on Android 11, where v21.0 did not before.
squabbi
on 10 Oct 2020
Still no progress with MM (310) (12) and M (21004). No root for my Android 10 device.
Phone: Oukitel WP5-PRO_EEA_V03_20200723
Baseband version: MOLY.LR12A.R3.MP.V114.9
kernel = 4.9.190+
Android 10
A/B = No
SAR = Yes
Ramdisk = Yes
magisk_install_log_2020-10-12T11_47_34Z.log
Alpamayo57
on 12 Oct 2020
+1 on an OP8 Pro / Qualcomm device, can't get it working, either bootloop or installed N/A
JoelJoos
on 15 Oct 2020
Phone: ONN Surf 10
Model:100003562
kernel = 4.9.190
Android 10
A/B = No
SAR = Yes
Ramdisk = Yes
I patch the boot img with magisk, flash to patched, boot is fine and manager states N/A.
Keloku
on 16 Oct 2020
Canary build 21004 works fine without any issue in Pixel 4 XL running Android 11 RP1A.201005.004.
shmshd
on 17 Oct 2020
Still it reports N/A with MM (311) (13) and M (21005). No root for my Android 10 device.
Phone: Oukitel WP5-PRO_EEA_V03_20200723
Baseband version: MOLY.LR12A.R3.MP.V114.9
kernel = 4.9.190+
Android 10
A/B = No
SAR = Yes
Crypto = File
Ramdisk = Yes
Alpamayo57
on 17 Oct 2020
3024
topjohnwu
on 22 Oct 2020
@topjohnwu maybe you are referring to #3042?
kidonng
on 22 Oct 2020
Can people test out the latest canary build and see if it fixes the issue?
k30 5g （sd765g） 21002 fix confirmed. really thanks for your work.
How do did u do it?
infinixs5lite
on 30 Oct 2020
Related issues
guitardedhero
·
3Comments
HikariCalyx
·
3Comments
Ralozey
·
4Comments
HikariCalyx
·
3Comments
Kratos291
·
3Comments