Magisk General Support / Discussion

[535iu]

You omitted the most important details like model, firmware

Assuming ramdisk.img, you should have Huawei with exactly EMUI 8.x?

Do you still have your ramdisk patched with the old Magisk - to revert if neccessary.
Try (re) patching with the new Magisk that ramdisk img previously (successfully) patched by the old Magisk, instead of patching the stock ramdisk

Try also with Magisk Canary (it's newer than Stable)

Use the appropriate (Stable or Canary) Magisk app

Hi. Yes, I have a Huawei Mate 10 8.0.0.

I have tried patching the original ramdisk and the last patched ramdisk (20.4). Nothing worked. Magisk and Magisk Canary patch the ramdisk wrong.

It's strange, because when Magisk/Canary patches the ramdisk wrong, the size of the file obtained is the same as the original ramdisk: 16 MB. However, in the old ramdisk patched correctly, the size was reduced: from 16 MB to 8 MB.

Is it possible that new versions of Magisk are not compatible with my phone? I currently have v20.4. The latest version of Magisk is 22.1. For example, if my phone was only compatible with version 21.0 (at most), how could I patch the ramdisk to version 21?

(Sorry for my bad English).

 

[zgfg]

Hi. Yes, I have a Huawei Mate 10 8.0.0.

I have tried patching the original ramdisk and the last patched ramdisk (20.4). Nothing worked. Magisk and Magisk Canary patch the ramdisk wrong.

It's strange, because when Magisk/Canary patches the ramdisk wrong, the size of the file obtained is the same as the original ramdisk: 16 MB. However, in the old ramdisk patched correctly, the size was reduced: from 16 MB to 8 MB.

Is it possible that new versions of Magisk are not compatible with my phone? I currently have v20.4. The latest version of Magisk is 22.1. For example, if my phone was only compatible with version 21.0 (at most), how could I patch the ramdisk to version 21?

(Sorry for my bad English).

Suggested you to try using Magisk Canary, which is 22104. Not guarantee but worth to try (if nothing else works)

Also, suggested you to try patching your ramdisk img that you previosly (successfully) patched with Magisk 20.4 - if that img was 8 MB, once you repatch by the new Magisk it will likely stay 8 MB

(Although the size should not matter that much - stock images are filled by zero bytes to the full size. Old Magisk cut off the filler bytes, while the new Magisk keeps the full size patched images)

Unfortunately, Magisk guides practically says that Huaweis are no more supported (if I recall correctly) because of troubles with unlocking the Huawei Bootloaders. If so, you are probably on your own to experiment with Stable and Canary, repatching the patched ramdisk instead of the stock one, etc

If nothing would work, you can stay with the old Magisk that happily worked for you - don't be concerned about SafetyNet showing API error and thus failing - you can use a third party SN checker and it should pass. Or just update Magisk app to Canary but stay with the old Magisk (the apk, former Manager, performs SN check and it fails there with the old one because of the old API key, needed for testing and nothing else

 

[Tanvir Rezwan]

If you have Systemless Hosts, disable or remove it from modules.

OTTOMH this is a major cause of instability in kernels with f2fs loopback bug present.

If your kernel has this bug, there may be other causes also, especially other Magisk modules. PW

The problem not fixed. i removed systmless host module but still after 20 - 24 hours pubg stuck and lagged
but all other thing is ok.

 

[pndwal]

The problem not fixed. i removed systmless host module but still after 20 - 24 hours pubg stuck and lagged
but all other thing is ok.

Seen this?:
https://xdaforums.com/t/pubg-crashing-fixed-on-rooted-phones.4073331/

Seems pubg now detects root, but doesn't Give any error, just crashes.

So you need to hide root from pubg like any security centric bank app. My method:
https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84936057

Nb. Hide / wipe order.

Additionally, seems you also need to hide Magisk App according to 'pubg-crashing...' thread OP.

Nb.2. OP there may be confused about the need for MagiskHide Props Config module. It shouldn't make ANY difference unless props are also 'configured' (added / altered) through its terminal emulator interface, but OP hasn't indicated any changes to make / configuration. (I could be wrong, but try first without it.)

Hope this one helps! PW

 

[pndwal]

Hi. Yes, I have a Huawei Mate 10 8.0.0.

I have tried patching the original ramdisk and the last patched ramdisk (20.4). Nothing worked. Magisk and Magisk Canary patch the ramdisk wrong.

It's strange, because when Magisk/Canary patches the ramdisk wrong, the size of the file obtained is the same as the original ramdisk: 16 MB. However, in the old ramdisk patched correctly, the size was reduced: from 16 MB to 8 MB.

Is it possible that new versions of Magisk are not compatible with my phone? I currently have v20.4. The latest version of Magisk is 22.1. For example, if my phone was only compatible with version 21.0 (at most), how could I patch the ramdisk to version 21?

(Sorry for my bad English).

There have been previous issues where zero padding causes problems, but I don't see any known ones currently.

However, these two issues may (probably) be affecting you (actually seems to be one issue, first running Android 8 EMUI like you, second running Android 9 LOS16.0):
https://github.com/topjohnwu/Magisk/issues/4297

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

Just been labelled a Regression, and @osmosis appears to be on it.

If the regression is in this commit of 4 May 2020:
https://github.com/topjohnwu/Magisk/commit/0c99c4d93f638d5cde9a232321af791c54be278b
as user indicates (and this is your problem), last working Public Stable Magisk for you will, in fact, be 20.4.

It's surprising it's taken this long to be reported!... Guess there may not be many Huawei users testing Canary. PW

 

[pndwal]

After updating to a.61 from a.59, there was a bootloop ( a.59 was rooted with magisk patched image), but after download a.61 update from realme website and then flashing original boot image, it worked, but my device is no longer rooted and safety net cts profile fails.
Tried rooting a.61 but there is a boot loop (even though performed same earlier method).
Device details attached.View attachment 5301757

I'm guessing you didn't Restore Images to take OTA? - you need unaltered read-only partitons such as /system, /vendor, /recovery, /boot to take stock OTA.

Generally, flash stock Recovery if using TWRP, and Uninstall Magisk using Restore Images function.

Next, seems you flashed boot.img from earlier .59 build? (So you're on .61 w/ old boot image?) ... Patching non-matching boot.img may be causing latest bootloop. You need to patch boot.img for current ROM build.

Sorry if I misunderstood what you've done, but you've given very little away! PW

 

[pndwal]

'And now for something completely different' ... and controversial ... and OT, except that it goes to OP's (not entirely unrelated) interests ... in a fellow techie's interests ...

... I'll just post a link:
www.twitter.com/topjohnwu/status/1390536971894751234

Sorry. (... Tried to warn you!) PW

 

[SaikiK]

Hello, thank you for replying. I don't know how to restore earlier images as phone is updated. My phone is working fine, I restored new a.61 boot.img only. But after patching this file by magisk, I ran into boot loop. Then restored original a 61 boot.img and it works fine. It's just that patched boot.img is not working.

 

[Xellerate]

After patching the entire ap file from stock firmware, and then flashing it, my android boots up without the touchscreen working, this can only be avoided by flashing a patched boot.img even though magic app states that i don't have a ram disk, and when I flash a patched recovery it says vbmeta not verified

 

[535iu]

Suggested you to try using Magisk Canary, which is 22104. Not guarantee but worth to try (if nothing else works)

Also, suggested you to try patching your ramdisk img that you previosly (successfully) patched with Magisk 20.4 - if that img was 8 MB, once you repatch by the new Magisk it will likely stay 8 MB

(Although the size should not matter that much - stock images are filled by zero bytes to the full size. Old Magisk cut off the filler bytes, while the new Magisk keeps the full size patched images)

Unfortunately, Magisk guides practically says that Huaweis are no more supported (if I recall correctly) because of troubles with unlocking the Huawei Bootloaders. If so, you are probably on your own to experiment with Stable and Canary, repatching the patched ramdisk instead of the stock one, etc

If nothing would work, you can stay with the old Magisk that happily worked for you - don't be concerned about SafetyNet showing API error and thus failing - you can use a third party SN checker and it should pass. Or just update Magisk app to Canary but stay with the old Magisk (the apk, former Manager, performs SN check and it fails there with the old one because of the old API key, needed for testing and nothing else

There have been previous issues where zero padding causes problems, but I don't see any known ones currently.

However, these two issues may (probably) be affecting you (actually seems to be one issue, first running Android 8 EMUI like you, second running Android 9 LOS16.0):
https://github.com/topjohnwu/Magisk/issues/4297

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

Just been labelled a Regression, and @osmosis appears to be on it.

If the regression is in this commit of 4 May 2020:
https://github.com/topjohnwu/Magisk/commit/0c99c4d93f638d5cde9a232321af791c54be278b
as user indicates (and this is your problem), last working Public Stable Magisk for you will, in fact, be 20.4.

It's surprising it's taken this long to be reported!... Guess there may not be many Huawei users testing Canary. PW

Thank you. I have exactly the same problem as in the first link, the only difference is the phone model.

I assume that if the bug in the second link is fixed, it will also work for the problem in the first link.

Does the "regression" tag mean that the problem will be fixed?

Until recently, I had no plans to update Magisk. However, I need to successfully pass the SafetyNet filter. I have read that the latest version of Magisk allows to succeed with SafetyNet. It is possible that SafetyNet is the reason why other users want to upgrade Magisk after such a long time and have taken the time to report it on GitHub.

Do you think the problem will be fixed, maybe in the next release?

 

[pndwal]

Hello, thank you for replying. I don't know how to restore earlier images as phone is updated. My phone is working fine, I restored new a.61 boot.img only. But after patching this file by magisk, I ran into boot loop. Then restored original a 61 boot.img and it works fine. It's just that patched boot.img is not working.

Ah, got it now. Sorry, misunderstood ' original boot image'.

Done some checking into your model and build numbers. Seems you have Realme C3, and Update was to Android 11.

Looks like you have a now known issue:
https://github.com/topjohnwu/Magisk/issues/4313

User @HemanthJabalpuri posted here too:
https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84963087

Might just have to watch that one. PW

 

[zgfg]

Thank you. I have exactly the same problem as in the first link, the only difference is the phone model.

I assume that if the bug in the second link is fixed, it will also work for the problem in the first link.

Does the "regression" tag mean that the problem will be fixed?

Until recently, I had no plans to update Magisk. However, I need to successfully pass the SafetyNet filter. I have read that the latest version of Magisk allows to succeed with SafetyNet. It is possible that SafetyNet is the reason why other users want to upgrade Magisk after such a long time and have taken the time to report it on GitHub.

Do you think the problem will be fixed, maybe in the next release?

If your 'problem' is Magisk mngr/apk showing API error for SafetyNet - simply don't mind (don't do SN tests from Magisk mngr/apk), use 3rd party SN checkers instead (available on Google Play) or just install the latest Magisk Canary apk (instead of your old Manager) but keep the Magisk that works for you

SN API error is because the SN key has expired. Every app that wants to do SN tests must register a key with Google - and that key has expired in the old Mngr.
But it has nothing with any other app that will do its own SN test (with its own key)

 

[pndwal]

There have been previous issues where zero padding causes problems, but I don't see any known ones currently.

However, these two issues may (probably) be affecting you (actually seems to be one issue, first running Android 8 EMUI like you, second running Android 9 LOS16.0):
https://github.com/topjohnwu/Magisk/issues/4297

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

Just been labelled a Regression, and @osmosis appears to be on it.

If the regression is in this commit of 4 May 2020:
https://github.com/topjohnwu/Magisk/commit/0c99c4d93f638d5cde9a232321af791c54be278b
as user indicates (and this is your problem), last working Public Stable Magisk for you will, in fact, be 20.4.

It's surprising it's taken this long to be reported!... Guess there may not be many Huawei users testing Canary. PW

Thank you. I have exactly the same problem as in the first link, the only difference is the phone model.

I assume that if the bug in the second link is fixed, it will also work for the problem in the first link.

I think both issues, "I lose root privileges after updating" & "Magisk framework does no longer start up" describe the same problem, so my guess is that the fix will also be the same.

Does the "regression" tag mean that the problem will be fixed?

Means a change caused a reversion of working function(s).

Until recently, I had no plans to update Magisk. However, I need to successfully pass the SafetyNet filter. I have read that the latest version of Magisk allows to succeed with SafetyNet. It is possible that SafetyNet is the reason why other users want to upgrade Magisk after such a long time and have taken the time to report it on GitHub.

Do you think the problem will be fixed,

Yes.

maybe in the next release?

$64 000 question!

Depends on colaborators time, priorities, schedule, access to diagnostic data, on John, holidays planned, covid19, the weather...

Best watch those spaces / contribute if you can! PW

 

[pndwal]

After patching the entire ap file from stock firmware, and then flashing it, my android boots up without the touchscreen working, this can only be avoided by flashing a patched boot.img even though magic app states that i don't have a ram disk, and when I flash a patched recovery it says vbmeta not verified

It's a Sammy? Magisk App says SAR Yes?

A checklist:
- Did you patch AP with Recovery mode selected?
- Did you do full data wipe w/ initial Magisk installation?
- Avoid MTP transfer?
- Flash the other files, not just AP?

Method:

Initial Magisk installation:
- Patch AP tar w/ Recovery mode selected.
- Copy the patched tar file to your PC with ADB (NOT MTP).
- Using Odin, flash magisk_patched.tar as AP, TOGETHER WITH BL, CP, and CSC (NOT HOME_CSC) to flash w/ data wipe.
- Allow Additional setup from Internet.

If updating ROM:
- pre-patch AP w/ Recovery mode selected.
- Copy the patched tar file to your PC with ADB (NOT MTP).
- Using Odin, flash magisk_patched.tar as AP, TOGETHER WITH BL + CP + HOME_CSC to upgrade / keep data.
- Allow any Additional setup from Internet.

... If you did do all that without success, please give details of phone / ROM, and Sammy users may chime in. PW

 

[SaikiK]

No it's android 10 only and realme ui 1

 

[pndwal]

No it's android 10 only and realme ui 1

Ah, I read this:
https://c.realme.com/in/post-details/1377151834564694016
and assumed again.

Problem with a.61 build is still very likely the same as issue on GitHub (both update privacy/security with latest changes, and both OTAs are incremental updates from RMX2027_11.A.59), so you may wish to comment in that issue thread.

Also, you may still have issues resulting from applying OTA without restoring images (Magisk Installed), but I'd say this is less likely. Boot image was clearly messed up by incremental OTA, but you've replaced that...

You may want to try flashing complete ROM (dirty flash) to check if it helps now that you have a.61 complete ROM package. PW

 

[artyfarty]

Hi, anyone in italy have problem with Credem home banking app? App found root (and close itself) even if magisk Is hidden root ti app and with anonymous package.

I have twrp too, on oneplus nord

Thanks

 

[pndwal]

Hi, anyone in italy have problem with Credem home banking app? App found root (and close itself) even if magisk Is hidden root ti app and with anonymous package.

I have twrp too, on oneplus nord

Thanks

Cleared data since?

This, or something else here may help:
https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84936057 PW

 

[SaikiK]

Full stock rom of a.61 is not available on the internet rn.
Also there is no twrp for realme c3 atm iirc. So I can't flash any zips.

 

[ipdev]

Full stock rom of a.61 is not available on the internet rn.
Also there is no twrp for realme c3 atm iirc. So I can't flash any zips.

Hi.
I am not familiar with Realme.

I did a quick check and see there is TWRP build over in the Realme C3 forums.
[RECOVERY][TWRP][RMX2020] TWRP 3.5.2 [UNOFFICIAL] - xdaThread - Link

Looks like it has only been out for a month and I am the only one who hit the like button so far. ​

Quite a few custom rom threads but, I did not see a thread for Stock rom / firmware.
Realme C3 - xdaForum - Link

Hope this is the correct TWRP for your device.
Cheers.

Edit:
@SaikiK
I see, you device might have rollback protection.
To be safe, you might want to ask in the C3 TWRP thread before you try it.