yashsingh1/xdaforums huggingface dataset:
[Magisk] dronkit:
Me and several people at the galaxy a32 4g forum had the following problem.

Rooted said phone with magisk using a patched AP file, and inmediately or after a few days of using it, we got IMEI and baseband unknown.

In my case I can say the original baseband was AUJ4 and the magisk version was 23.0 at the time. After the problem I tried a lot of combinations of reflashing the stock firmware, refpatching and flashing the magisk patched firmware, lock, unlock bootloader, then got an update with baseband AVA1 and got Magisk 24 and 24.1, tried all that to no avail.

Someone in a thread said reverting to AUG baseband fixed it for him, but me and other cannot downgrade to taht version because the one our phones came with have a later baseband and the phone doesn't allow flashing AUG.

Browsing the phone I find I have an EFS directory but not the IMEI folder of file they say i'm supposed to have, and no /data/nvram or similar folder, nor /dev/nvram.

Maybe Magisk is not the culprit here, but I'm writing here because I got strange messages in the Magisk log (attached) of which I find almost nothing on forums or the web. It seems it tries to "unlock" (whatever that means) several partitions or devices but gets "permission denied", for example:

unlock mmcblk0p42 failed with 13: Permission denied

Does anyone know what can I do to fix this and regain my IMEI and baseband, preferently still get root?

Thanks!
[Magisk] pndwal:
Please say what you flashed...

Did you

- Follow official instructions to flash all components in Odin incl. CSC for full data wipe w/ initial root?

- Use AP exactly matching /extracted from current ROM archive?

- Do file transfer using ADB, NOT MPT? PW
[Magisk] jons99:
also magisk hide is removed from the latest alpha
[Magisk] Homeboy76:
I tried to sideload the Magisk-alpha app-release.apk after I changed the apk to zip. It failed the error was meta file missing...

Was I supposed to sideload the Magisk alpha zip file?

Phone; Pixel XL

Android 10

Linage 17-1
[Magisk] jons99:
if you're already rooted then you can uninstall the magisk app and install the magisk alpha app and do a direct install
[Magisk] eXtremeDevil:
Sorry if this has been answered before, but what is the meaning of "Restriction on non-SDK interfaces is not working" in Momo? Maybe a MIUI thing?
[Magisk] zgfg:
I have that non-SDK, Partition nounted abnormally, and Bootloader unlocked with Xiaomi.eu

On the other phone, stock MIUI, only BL unlocked
[Magisk] eXtremeDevil:
Partition mounted abnormally is due to core patch, like disable signature verification. About non-SDK, I think it could be the ROM but I can't know for sure.
[Magisk] zgfg:
On my both phones I have only Smali patcher for Secure screenshots

With stock MIUI, Partitions mounted abnormally are not reported (even with Smali patcher installed and enabled)

On Xiaomi.eu it is detected, and even if I remove Smali patcher

But Momo does not bother me at all
[Magisk] Homeboy76:
The phone is not rooted. It was a test to see if

Magisk-alpha

could be sided loaded like

Magisk-canary

can, during the installation or manual updating process of lineage 17.1 for marlin.

Thanks for responding!
[Magisk] Eng.Raman:
https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86056379
[Magisk] eXtremeDevil:
Thank for the info, very useful!
[Magisk] Svirusx:
Hey, i have question about Magisk for Samsung GSI exactly Samsung Galaxy s20 FE 5G (Snapdragon) here is only one version which works on GSI for this model https://github.com/topjohnwu/Magisk/files/7819803/app-debug.zip are here source code of exactly this version of magisk? I want to try compile latest magisk for GSI but i can't vind any tag of this version source code. (Success compiled latest magisk Yee)
[Magisk] zgfg:
If you have it installed, you would know was that Stable or Canary, and the full version name .

If not too old, you should be able to find the tag (based on the version name) in Github and fork the code.

Some older versions might have been archived, but still possible to find
[Magisk] zzz2002:
Device Samsung Galaxy S7 edge (hero2lte) .

I have just wiped and reinstalled stock firmware using Odin 3.14.4, firmware version/id G935FXXU8ETI2 - downloaded from SamMobile. Started and ran stock SW, behavior normal.

Added TWRP, Installed Ivan Meller's Lineageos-19.0 20220127 + NikApps 20220127.

Everything seems normal except YASNAC reports both basic and CTS - PASS, and RootBeer reports everything except test keys + dangerous props, are OK (check marked).

Can somebody tell me if this is normal as I HAVE NOT YET installed any part of Magisk.

I had installed it on a previously LineageOS setup, but I was under the impression that installing a stock ROM should have removed all traces of prior setups.

edited@13:33
[Magisk] Spartacus500:
Show screenshots from Root Bear and YASNAC
[Magisk] Svirusx:
Got version

Installed: 7a8237a3 (23016)

in canary releases isn't 7a8237a3 (23016) version but 92546e8a (23016) :/ looks like fork or custom build hmm
[Magisk] pndwal:
Official LOS will never spoof CTS profile match (doctor certified fingerprint) or build with patches like @kdrag0n's USNF etc due to strict policy re. manipulating signals (like policy John adopts now). These will generally need Magisk framework + modules like USNG to pass SafetyNet. Nb. Official LOS can still pass SafetyNet natively for the time that fingerprint prop date matches security patch date, if this initially matches by coincidence, and ROM is for a device w/o hardware key attestation implemented (old LV Android 7-, some OnePlus (OEM botched implementation) devices etc).

Other custom ROMs incl. unofficial LOS often integrate such spoofing / manipulation etc. Method for integrating USNF is linked in @kdrag0n's GitHub and developed for his own Proton ROMs.

🤠 PW
[Magisk] xunholyx:
Anybody try installing Magisk on Android 13 yet, or am I going to be the guinea pig? I'm downloading it now. I'm not sure if I'll have time to flash it tonight though. Tomorrow I will
[Magisk] Lughnasadh:
A few people have reported that Magisk is working on Android 13 DP1 (Pixel 6/6 Pros).
[Magisk] xunholyx:
COOL!!!

I'm on the P5 but it should still work.
[Magisk] zgfg:
My MiXplorer correctly opens all folders on /data, /cache, etc

On both phones, new Lisa (Xiaomi 11 Lite 5G NE) and the old Davinci (Xiaomi Mi 9T), both running MIUI 12.5+, A11

Try the following, in Magisk app, go to SuperUser tab, scroll to MiXPlorer, long press and Revoke

You would maybe better then also Wipe Data for MiX (Settings, Apps), open MiX again, enable and grant root and try again

But I will later comment more about MiX and some changes I observed between Magisk 23016 or 23017 (not sure) and 24102
[Magisk] dronkit:
at first I used the very same stock rom that came with the phone, same csc, magisk 23, patched the AP and i'm sure it was the same, and flashed all four files, including csc. The thing is, that time I used MTP.

Do you think it's corruption when you get no IMEI and those permission denied errors?

the next tries I used MTP but i did MD5 checks before and after transfer. I used Magisk 24.0 and 24.1 and the stock rom I mentioned and then an updated one, the update came recently.

I can try to patch and flash the current stock rom with the latest magisk canary, using only ADB for transfers. Do you think that would work?

Thanks for your reply.
[Magisk] zgfg:
More about MiXPlorer and Magisk v24102

I have observed (same two phones) that patching the boot.img sometimes works, and sometimes fails with:

-Copying to Cache

-Ptocess error

At first I was not sure since there are two phones (one with 20 MB boot.img, the other with 192 MB boot.img - altough I shared imgs between asking one to patch for the other), there were Magisk updates, etc

But I opened a Github ticket:

Patching boot.img fails (Copying to cache, Process error) · Issue #5429 · topjohnwu/Magisk

Device: Xiaomi 11 Lite 5G NE (Lisa) Android version: 11 Magisk version name: Canary Magisk version code: 24102 Stock MIUI 12.5.8 Global I'm not able to patch the boot image, it always fails with: C...

github.com

and thanks to the hint from @yujincheng08, I have carefully retested:

- If I use the stock Files explorer, patching works on both phones with no problem

- Reported Copying to Cache / Process error happens on both phones but only if I use MiXPlorer

However, on my old Davinci (daily driver for two years) I always used MiXplorer (I had stock Files frozen) and never observed any problem with patching, up to Magisk Alpha 23016 or 23017

When I obtained the new Lisa I first also installed Alpha 23016 or 23017 apk and I was able to patch.

However a week later, when Bootloader was unlocked, I already moved to the next Alpha and I was no more able to patch (I continued to use MiXPlorer)

Hence on two phones:

- Always the same MiXPlorer version (I do not update, I like a particular little bit older version I use)

- Phones are different models hence run different firmwares but both MIUI 12.5+, A11 and I didn't upgrade the ROM on either phone (there wete no upgrades in the meantime)

- I usually put the boot.img to Download folder, but I carefully tested now by using various folders on Internal memory and various names for boot.img (even with boot.emmc.win as backed-up from TWRP)

- With Magisk up to 23016 or 23017 (not sure did it work with Alpha 24101), patching boot.img with MiXPlorer worked fine on both phones

- but now with 24102 (on the old Davinci Magisk Alpha, on the new Lisa Magisk Canary - I switched last evening from Alpha) patching by navigating through MiXPlorer to the boot.img fails while Copying to Cache
[Magisk] m0han:
you could try whether the latest MiX version (magically ;)) addresses this issue. or, is there a problem with that?
[Magisk] zgfg:
Maybe over the weekend, but as said, I don't like some changes in MiXPlorer the dev made over the last year (it's an awesome app but I really need only a fraction of its functionalities)
[Magisk] avalx:
I found out there are some magisk related directories in the /data (see screenshot) - looks to me like some kind of backup of boot images?

Any ideas if this should be kept (some are quite old and probably not relevant anymore) or are they safe to delete?
[Magisk] Lughnasadh:
Think those are the stock boot images that Magisk backs up. Think they are used by Magisk when uninstalling and restoring stock boot image functions. I wouldn't delete them.
[Magisk] zgfg:
As answered, boot images Magisk saves.

I always delete - keeping only the latest
[Magisk] zzz2002:
Here are the screenshots. I tried using X-plore to explore the storage on my device but it does not work (well) because it cannot get root access.
[Magisk] Danny94:
Device: Redmi k20 Pro

Rom: Miui v10.3.3 Global stock

Magisk 24.1.apk

Ramdisk: no (according app)

vbmeta partition: yes (vbmeta)

Installed via recovery mode and selected the recovery.img from extracted rom (Miui v10.3.3 Global stock).

Booted into fastboot, flashed modified file into recovery partition.

success

result:

Now if i reboot with Power + volume up i am booting into Magisk system.

The app says installed 24.1, i have enabled Zygisk aswell.

Rootbeer still says im rooted:

-SU Binary

-2nd SU Binary check

-For RW Paths

-Root via native check

-Magisk specific checks

How to get passed ?

EDIT: Oh im stupid i have not configured the DenyList for rootbeer

And i have discovered if i miss a single time to hold down the keys correctly my phone instantly replaces my modified recovery with stock and have to redo everything... is there a way to prevent this ?
[Magisk] zgfg:
Although it says Ramdisk No, it has really been reported elsewhere (and specially in this thread) that for Xiaomi phones you need to patch boot img with Magisk

You can flash TWRP or stock recovery, and install Magisk to Boot - then you would normally boot to Magisk

(Responding you from Mi 9T not-Pro, also with Magisk v24.1 but installed to Boot)
[Magisk] Danny94:
No for me its working now all good, i dont even have to press the buttons anymore on reboot or shut off/on.
[Magisk] mierdaseca:
So I updated magisk 23 --> 24.1 directly from the app, after reboot, wifi isnt working but data is. So I reboot again and now it asks for a decryption password which I dont know (i tried pin code).

I need help. I dont wanna lose all the data.

Device is a Redmi Note 7 with latest xiaomi.eu
[Magisk] Eng.Raman:
New Shamiko-v0.4.3-102 released by Magisk alpha TG Channel. ( attached ).

No change log yet.
[Magisk] m0han:
yeah. new alpha and zygisk-lsposed too.
[Magisk] zgfg:
All again ok (patching by navigating to boot.img by MiXPlorer) with the new

MiXplorer_v6.58.4_B22020910.apk
[Magisk] Spartacus500:
If all Banking and other root detection applications are working for you, I would not be a problem 🙂 If you can, show the screen from the MOMO 4.0.1 application 🤔
[Magisk] zzz2002:
Dumb ? Where can I find/get mono?
[Magisk] martyfender:
The way I understand it, we are not supposed to post links. If you search for github momo coolapk, you can find it.
[Magisk] zzz2002:
Thanks I will take look on github.
[Magisk] zzz2002:
Can TWRP be used to flash a boot image taken from a firmware bundle.Would this work as a fix for screwed up (un)installations.

---------

Up till now I have used either Odin or Heimdall.
[Magisk] pndwal:
Depends what's borked.

Not needed if Magisk db file or other configuration in /data/adb directory is the issue; just delete all content there. Magisk daemon will rebuild configuration on reboot unless it's uninstalled.

If bad boot image, flashing from twrp can work on many devices, but NOT late Samsung (Android 9+ launch version?).

Important Notes​

Never, ever try to restore either boot, recovery, or vbmeta partitions back to stock! You can brick your device by doing so, and the only way to recover from this is to do a full Odin restore with data wipe.

To upgrade your device with a new firmware, NEVER directly use the stock AP tar file with reasons mentioned above. Always patch AP in the Magisk app and use that instead.

Never just flash only AP, or else Odin may shrink your /data filesystem size. Flash AP + BL + CP + HOME_CSC when upgrading.

https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root

So to fix bad Magisk installation in later Samsung devices, patch stock AP again and flash 4 components as above.

To fully uninstall Magisk or fix bad un-installation in later Samsung devices, a full data wipe is needed. - Flash stock AP + BL + CP + CSC.

🤠 PW
[Magisk] pndwal:
I still find the rules here extremely confusing.

Mods often quote obscure mandates (for example from device forums) such as @TNSMANI's blanket 'no links from social media but quoting is alright' rule (No-on answered my query on the official 'no copying and pasting' rule either...), or or just make their own blanket rule such as @Didgeridoohan's replacement of the above rule, "linking/quoting social media posts (or other webpages for that matter) is perfectly fine (as long as they're on the straight and narrow, i.e. no warez or stuff like that). I don't care what's been said before, this is where we are at now..." I discussed these here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86083339

Next we had:

Since there simply was no "intention of selling something" there, I can only assume that the objection to TG links is subclause stating that users should not need to register (sign up for account)... This is strange to me since Devs are expressly allowed one TG link in development threads on XDA. 🤔 ...This also limits @Didgeridoohan's stance a bit...

Anyway, since webpage for vvb2060's Momo doesn't need registration, I'll post it next... I think I can still copy/paste it too, since I'm not quoting anyone! 😬 Yikes! PW
[Magisk] pndwal:
Here: Momo, "The strongest detection app known"... PW
[Magisk] pndwal:
Latest Shamiko

Shamiko-v0.4.3-102-release (Release Notes same as for Shamiko-v0.4.3-100-release):

# Shamiko

こっっ…　これで勝ったと思うなよ―――!!​

### Introduction

Shamiko is a Zygisk module to hide Magisk root, Zygisk itself and Zygisk modules like riru hide.

Shamiko read the denylist from Magisk for simplicity but it requires denylist enforcement to be disabled first.

_Currently, system apps (with uid%100000=1000) cannot be hidden even it's in the denylist. This issue comes from Magisk._

### Usage

1. Install Shamiko and enable Zygisk and reboot

1. Configure denylist to add processes for hiding

1. *DO NOT* turn on denylist enforcement

#### Whitelist

- You can create an empty file `/data/adb/shamiko/whitelist` to turn on whitelist mode and it can be triggered without reboot

- Whitelist has significant performance and memory consumption issue, please use it only for testing

- Only apps that was previously granted root from Magisk can access root

- If you need to grant a new app root access, disable whitelist first

### Changelog

#### 0.2.0

1. Support font modules since Android S

1. Fix module's description

#### 0.3.0

1. Support whitelist (enable by creating an empty file `/data/adb/shamiko/whitelist`)

1. Always unshare (useful for old platforms and isolated processes in new platforms)

1. Request Magisk 23017+, which allows us to strip Java daemon and change denylist regardless of enforcement status

1. Temporarily disable showing status in module description (need to find a new way for it)

1. Support module update since Magisk 23017

#### 0.4.0

1. Add module files checksum

1. Bring status show back

1. Add running status file at `/data/adb/shamiko/.tmp/status`

### 0.4.1

1. Add more hide mechanisms

### 0.4.2

1. Fix app zygote crash on Android 10-

### 0.4.3

1. Fix tmp mount being detected

Appended notes from TG:

0.4.3

1. Fix tmp mount being detected

2. Hide modified traces of init.rc

Note: Hiding some system apps won't work since 0.2.0. It is a Magisk's bug, and it has been fixed since 24102+.

NB. GitHub host has not been updated with v0.4.3-102 release at this time. Please check for changes:

https://github.com/LSPosed/LSPosed.github.io/releases

Latest is in Alpha Magisk Telegram thread, but Oswald Boelcke (see rule cited in my post above) prohibits linking TG.

👍 PW
[Magisk] pndwal:
Good to know you have Magisk in recovery working on Xiaomi.

Previously, many with Ramdisk = no found this method failed, but successful installed Magisk in boot once they discovered that this does in fact work despite Ramdisk = no.

Nb. Magisk is actually showing if OEM Ramdisk in recovery = yes or no. Since recent Magisk installs a basic ramdisk if missing, ramdisk in boot will actually now = yes if boot.img is patched, but OEM ramdisk in boot (displayed) = no. This is correct behaviour because the new ramdisk for these devices generally fails to function due to bootloader incompatibly. In the case of Xiaomi and a few other devices, the bootloader is inexplicably compatible allowing for Magisk in boot despite Ramdisk = no displayed.

Anyway, seems something may have changed in Magisk to allow this method to work in Xiaomi; I always thought it should since installing either to boot or to recovery should possible in these cases as we now have a working ramdisk in both... I may try again to install Magisk in recovery on my RN8T (ramdisk = no but working in boot) sometime just for kicks!

This issue also affects initial installation of custom recovery on many devices. Seems the file: /system/bin/install-recovery.sh present in stock system, or some newer trick, is responsible for that. (Here's an old post about it: https://xdaforums.com/t/recovery-official-sagit-twrp-3-2-2-0-for-xiaomi-mi-6.3619822/post-72620133 )

To fix TWRP replacement with stock recovery by OS, the usual trick is to boot once into recovery using buttons (not 'fastboot boot twrp'), before booting to system to disable that feature in OS. I'm guessing the same trick should work for Magisk in recovery.

So booting to System with Magisk (via recovery) first: Try 'fastboot reboot' and immediately after device reboot, in black screen, hold VOL+ button. Alternatively, disconnect USB cable, then press and hold Vol+ and power button until recovery boots...

Ref here:

https://xdaforums.com/t/twrp-reverts-back-to-mi-recovery-3-0-every-single-time.3954753/post-80020975

[See also instructions in OP here:

https://xdaforums.com/t/twrp-3-4-0-...ro-redmi-k20-pro-stable.3944363/post-79823568 ]

An alternative solution is start fresh with root, and try installing Magisk in boot partition as for Ramdisk = yes devices as this generally works flawlessly on Xiaomi as discussed.

🤠 PW
[Magisk] Danny94:
@pndwal i am using an old rom maybe thats the reason (PIE), no clue but i tried it few times and had to setup up magisk and reboot a few times into magisk system until it worked permanently (maybe its working for each xiaomi device with a bit of stubborn).

At the moment i have another problem. My app Pokemon Go does not work. I have enforced it in the list but pokemon go uses play store/services stuff and i cant choose that in the list like in the old manager.

Aswell i downloaded YASNAC which says:

-Basic integrity fail

-CTS profile match fail

advice: Resotre to factory rom, lock bootloader

Is there any fix to make pokemon go working here ? Maybe i should use boot.img methode tough ? Or install another module ? (rootbeer still pass 100%)
[Magisk] zgfg:
Have you installed USNF 2.2.1?

Since you have custom ROM, to pass SN you may also need MHCP to spoof fingerprints, but first try with only USNF:

- Zygisk enabled

- Enforce DenyList disabled

- Shamiko installed

- USNF installed

- all other modules disabled

If still not passing you will need MHCP and spoof fingerprints as if you were on stock MIUI
[Magisk] pndwal:
Zy-USNF should do it. Think you have stock MIUI...

What modules are you running?... Is Zygisk working / enabled? ... Magisk in boot or recovery shouldn't matter here. PW
[Magisk] Danny94:
@zgfg @pndwal I have tried USNF downloaded from Magic Mask repo (seems to be v2.2.0), probably the wrong one, but i have no clue how to get all those modules these days beside that repo app.

Else i have installed installed ACC, Debloater, Systemless Hosts.

Edit: found the latest USNF on github, gonna try it now.

Edit2: Yeah that definitly did the trick, thanks a lot u 2 ;D.
[Magisk] zgfg:
USNF and MHPC have their own threads on XDA with links to GitHub.

But you could also google for GitHub + module name

Did you read OP posts in this thread (frankly, I didn't, but I think @ipdev was constantly updating them and put a lot of valuable info, links, etc)

Generally, install Fox Magisk Module Manager = Fox Mmm app, it will bring you the on-line modules functionality you are looking for (it merges from two repositories, eg you will find MHPC but not USNF in Fox)

PS: OP posts but not in this thread - there is a new thread devoted to the new Magisk with Zygisk
[Magisk] zgfg:
Sorry,.I meant OP posts in this new thread (people are discussing here and there):

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/
[Magisk] pndwal:
Trivial pursuit question; Who wrote this?:

Behavior changes: Apps targeting Android 13 or higher | Android Developers

Learn about changes in Android 13 that will affect apps when they target Android 13 or higher.

developer.android.com

😛 PW
[Magisk] zzz2002:
further screenshots, doesn't look "right"
[Magisk] zgfg:
Your device IS running custom ROM - few days ago somebody asked similar, you may search back about fixing addon.d

You could check by getenforce if your ROM maybe runs SELinux in Permissive mode

Data are encrypted, unsafe, old ROM

TWRP files - as it says, delete TWRP folder (or try by renaning to eg TWRP.back)

init.rc - if Shamiko does not help (?), try InitRcHider - please search yourself, read back, I canot play Google to find where did I read/download that module 15 or more days ago