Search the two Magisk threads, there's a command line option. There is also advice that you do not normally need it. I do not remember whether you do not need the function, or whether you do not need to ask for it because it is done automatically.
Yes I have the same issue. Since the Shamiko v0.5 update my banking App won't open. If I revert back to v0.4.4 my banking App works fine again and doesn't detect root, etc.
Are you possibly on a custom ROM? I have EvoX on two devices and both have this issue with Shamiko v0.5. However, I have one device one stock Samsung ROM and my banking App with the latest Shamiko works on that.
Can't figure out what the issue could be.
Surprisingly I found out what these numbers and letters are. I am from a pretty long time ago, and only recently tried again to root. This is what I found when flashing (I should have seen this earlier tbh):I figured I should post this here, and I am unsure if it is even supposed to happen. My phone is a XT1952-T, so a rebranded Moto G7 Play, and I am aware that the "bad key" and "N/A" appearing after an unlocked bootloader is normal. In my case though, these letters and numbers appear instead.
This always happens after flashing the magisk_patched file. Sometimes it ends up corrupting the phone, and other times it lets me get through, but Magisk still says N/A on installed. I am using the correct boot.img that I pulled directly from LMSA.
Whether I use TWRP or fastboot to flash it, this always ends up happening. I also flash the stock firmware with LMSA before flashing so that I ensure the previous test doesn't conflict with the next one. I don't ask for a fix, I am actually intrigued on why this happens, any ideas?
AFAIK vbmeta images will be essentially identical, but named for dual partitions... I believe you won't have "vbmeta" on A/B device... PW
Many factors...Good morning, I've updated my Samsung Galaxy Tab S5e today via OTA (LOS 19.1, MiindTheGapps, Magisk 24.3).
Although there is an addon.d script for Magisk, only the GApps were reinstalled, not Magisk. I had to do it again via adb.
What could be the reason? File-permissions of the script are fine.
Thanks for the hints. The device isn't A/B, TWRP isn't installed. I've used the inbuild LOS updater which rebooted into LOS recovery, installed the update, reinstalled GApps, but not Magisk. All addon.d scripts are in the same directory and have the same permissions.Many factors...
- If using TWRP, none are yet properly A12 compatible...
- LOS recovery can't decrypt /data
- For A/B devices (i.e. addon.d-v2) the OTA must be run through the system settings updater app rather than LOS recovery
- A/B (addon.d-v2) when using TWRP may only work in certain branches (note the date here) https://github.com/topjohnwu/Magisk/issues/3820#issuecomment-856937113
Nb. @osm0sis is the resident expert on all things addon.d (and designer of much of it) here.
Hope this helps. PW
Since that is about TWRP and custom ROM for your particular device, I think it should have been posted to the subforum for your phone, to the threads about your LOS (and TWRP), to the corresponding TG or Discord channels (whatever they have for support) and/or directly to those thread(s) you are quotingHello, this weekend I followed a tutorial to install TRWP see topic on XDA you have to install with trwp.apk.
I got the concern that lineage 19 under android 12 bug no play store stops and other bugs.
see these 2 links
Preamble When TWRP first appeared for the S10 range of devices, it quickly became clear that there were some major issues with the initial builds. Many users were understandably frustrated at losing the ability to boot their device after...forum.xda-developers.com
An early build of LineageOS 19.0 based on Android 12 is now available for the Exynos Galaxy S10 series. Download links in the post.www.xda-developers.com
Probably. I'd first look and ask where the TWRP is coming from.
Do you really think your problem is common for all phones (in that case nobody of us would use Magisk v24.3), or do we know by telepathy what is your phone, ROM, etc
OnePlus 5Do you really think your problem is common for all phones (in that case nobody of us would use Magisk v24.3), or do we know by telepathy what is your phone, ROM, etc
Problems like that are generally rare and very specific - only if you provide the relevant info somebody who is familiar with the phone, ROM type and so could provide you some help
Could be some anomaly w/ LOS recovery, eg hidden comment after this one:Thanks for the hints. The device isn't A/B, TWRP isn't installed. I've used the inbuild LOS updater which rebooted into LOS recovery, installed the update, reinstalled GApps, but not Magisk. All addon.d scripts are in the same directory and have the same permissions.
Symptom smacks of mismatched kernel... Did you ever install Magisk using Magisk App patch/flash? PW
No, I never had to uninstall a 'hidden' version. The installation is just one week old and yesterday it got the first OTA.Could be some anomaly w/ LOS recovery, eg hidden comment after this one:
Wondering, you didn't ever need to uninstall a 'hidden' (obfuscated) Magisk app after update to get things working did you?...
Also, did you install Magisk from recovery zip installer prior to OTA? (Never installed via app patch/flash)? PW
So could be the anomaly I noted above... Or this one I mentioned earlier:No, I never had to uninstall a 'hidden' version. The installation is just one week old and yesterday it got the first OTA.
Last week I installed LOS -> GApps -> Magisk.zip via adb. I did not flash a patched boot.img (I know that I will not get the script in this case).