yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Check this tool - check also recent posts with more about:

/data/adb/magisk/magiskboot --help

Not sure is it duable as you want (and frankly, I'm not familiar with)
[Magisk] moocow1452:
Not sure I can operate Magiskboot before I flash it to the device. Once I flash Magisk, I have access to fastboot through recovery, and that's it.
[Magisk] zgfg:
You can operate the tool with root, you give it boot.img (or patched one), hence maybe (but IDK) you could use it from another phone

And you can (re)pack the img - and later you flash to your target device
[Magisk] ipdev:
This one might be a bit more confusing. ;)

While catching up last night, I missed that you are not rooted. :oops:

---

Without root, you need a directory with heightened permissions that you can access.

You should be able to use the /data/local/tmp/ directory.

Unzip the Magisk apk file and push the appropriate architecture to the device.

Then set the permissions to be executable.

Linux/Mac command line example.

Make the appropriate changes if you use Windows.​

Unpack the lib directory from the Magisk apk file.

unzip app-debug.apk lib*​

Push the matching Magisk architecture to the device.

adb push lib/YourDeviceArchitecture/* /data/local/tmp/​

Push the boot image you want to modify to the device.

adb push boot.img /data/local/tmp/​

Set permissions.

adb shell chmod 0755 /data/local/tmp/*.so​

Enter adb shell and change directories.

adb shell

cd /data/local/tmp/​

Run the commands using the ./ prefix.

./libmagiskboot.so​

Make the changes you want, exit the shell and pull the new-boot image to the computer.

Reboot into bootloader and boot the new-boot image.

Note:

/data/local/tmp/ should be an empty directory.

You should clear the directory after you are done using it. ;)

Quick example just unpacking and repacking a boot image without root.

Magiskboot Example - Pastebin - Link

Hope it helps more than confuse. 🙃

Cheers. :cowboy:
[Magisk] pndwal:
A few new observations re. Magisk Safe Mode detection anomalies, especially on Xiaomi devices (but likely other also):

https://github.com/topjohnwu/Magisk/issues/4624#issuecomment-967787170 PW
[Magisk] pndwal:
@zgfg, initially I deleted my LSPosed Manager and still had shortcut to 'parasitic' manager working with no issues.

Now, however, I cannot seem to get this configuration back... Clicking 'create shortcut' seem to do nothing, if I uninstall the manager no shortcuts seem to remain...

Please can you tell me what I'm missing / what I've forgotten? PW
[Magisk] zgfg:
Sorry, I don't understand - do you still have a shortcut or now you have deleted and reinstalled, and now you cannot create shortcut anymore?

I have Riru-LSPosed 1.6.3 (6212) - it's boring for me to update several times a day when they rapidly push new versions to TG LSPosed, only shortcut and all ok.

But there is no option to Create shortcut from the shortcut, only from the LSPosed app

Anyway, you can invoke also by dialing *#*#LSPOSED#*#* aka *#*#5776733#*#* (double-check if digits correspond to the letters), and maybe if you deleted the app and didn't create shortcut, it will ask you to create

Btw, I think I needed to enable Create shortcut permission for the app first (before creating the shortcut and deleting)
[Magisk] pndwal:
Yeah, think I deleted manager when I moved to Zygisk module. Installed again from data/adb/lspd as message says. All then works fine, just don't know if Create shortcut from in-app dialogue actually does anything as I only see original shortcuts which disappear when I uninstall app. 😟

I'm on latest 1.6.3 (6219) ... Woops, no I'm not... now 6220

Yup, that's what I'm trying...

Ta, yes that works (even with App uninstalled)... at least I can get manager without app Being 'installed' (tip: Can even copy / paste code in Google Dialer), but I'd like to have shortcut back! 'Parasitic' manager from Dialer doesn't show Create shortcut dialogue for me...

Do you mean LSPosed settings 'Force apps to show launcher icons' (doesn't help) or other? I selected device settings Always allow home-screen shortcuts too - no dice. In app dialogue simply doesn't produce a shortcut on home-screen or elsewhere I can find... PW
[Magisk] zgfg:
Settings/Apps/<given app>/Permissions/Home screen shortcut

(A11, MIUI 12.5)

Screenshot for Magisk app, since my (parasitic) LSPosed is uninstalled and only the shortcut remained

Btw, probably you should be also able to create home-screen shortcut for the secret-code for dialer (workaround)
[Magisk] zgfg:
Interestingly, Momo is not available in source code on (his) Github page

Btw, anybody, with TEE device, able to hide Bootloader unlocked from Momo (4.0.1)?
[Magisk] pndwal:
Yup, that's what I did; green is "always allow"

Good tip, and indirectly helped me solve it! 😜

I'm using Smart Launcher 5 (which I love for its auto cataloguing apps).

Generally I add app links on home-screen using "Add Icon", and of course the LSPosed icon is there when installed as it is for all all other apps. After uninstalling it is gone however, which suddenly makes sense!

Since I was expecting LSPosed app to create shortcut on home-screen (I think it does for other launchers) I was searching with "Add icon" DUH!... Of course it's a shortcut!... And there it was in "Add shortcut"! 🤪

Better get more used to Smart Launcher... I might even write "Smart Launcher for Dummies".

Thanks for your help, n G'mornin to ya(?) 😜 PW
[Magisk] pndwal:
Probably there (or in RikkaApps GitHub), but 'private'. My guess is source is available for a fee. 😬🤪

Homepage sums up intentions (and states some detection methods are private)... if you can get your head around it! PW
[Magisk] zgfg:
Trying more a beginner's excersize. Playing with magiskboot on my rooted phone, repacking its own original boot and Magisk patched images

Copied my boot.img and patched.img to Internal memory Temp folder and executed:

/data/adb/magisk/magiskboot repack boot.img

Later tried also with -n option but obtained the identical new-boot.img (identical checksums)

new-boot.img is exactly the same size (21 MB) as my original boot.img, but when I flashed I ended up in Fastboot (not bootable)

I similarly tried repacking my boot img patched by Magisk, again the resulted img was the same size as original, but also not bootable

Mi 9T, Xiaomi.eu A11, Magisk Custom 23013

When I patch or do Direct install from that Magisk Custom apk, I obtain the correct, bootable (with Magisk installed) images.

Afaik, the apk should internaly use the same magiskboot tool

Am I doung something wrong?
[Magisk] shoey63:
what about

./magiskboot --unpack boot.img

Then

./magiskboot --repack boot.img

?
[Magisk] zgfg:
Thanks, with unpack action followed by repack it worked, actually I obtained the new-boot.img identical (same checksums) to the originating patched-boot.img
[Magisk] moocow1452:
New Canary, new behavior. I did a factory reset and a full sideload update on the Oculus Go just to be sure, but when I try to load this new Magisk boot, the device takes it, but the app doesn't seem to recognize that it has been rooted. I guess that's a step in the right direction, right?

Some logs if you want them:

(https://github.com/topjohnwu/Magisk/files/7532774/magisk_log_2021-11-13T.log)

(https://github.com/topjohnwu/Magisk/files/7532775/magisk_log_2021-11-13T16.log)

(https://github.com/topjohnwu/Magisk/files/7532776/magisk_patched-23014_cjK37.zip)

(https://github.com/topjohnwu/Magisk/files/7532777/magisk_install_log_2021-11-13T16.log)
[Magisk] pndwal:
Did you ever hide the Magisk app since factory reset?... Pls give screenshot of Magisk home screen. 👍 PW
[Magisk] moocow1452:
Unable to hide, treats it like it's completely unrooted. Screenshot is a little difficult since it's a VR headset.
[Magisk] pndwal:
Ah, I see... Think you get screenshot by winking 3 times in headset... (kidding...)

You seem to have "can't preserve ownership" issue. These search results may help you:

https://github.com/topjohnwu/Magisk/issues?q=is:issue+can't+preserve+ownership+ PW
[Magisk] moocow1452:
@pndwal Will look into it.

Super interesting. Unpacking and repacking a Magisk boot following your instructions did create a flashable boot that allowed the system to boot correctly, but root still seems to be elusive. Maybe the Magisk boot needs to be constructed within a directory with root permissions?
[Magisk] pndwal:
Just looking back here... It's Android 7?

I don't think AVB 2 / vbmeta exists pre Android 8...

Also, "can't preserve ownership" issue can apparently be a red herring if patching on unrooted device (just 'weird' result)...

Are you patching on same device or other? PW
[Magisk] moocow1452:
Oculus Go is on Android 7.1 and i'm patching on the same device. I don't have a rooted device to test with patching Magisk on that device. I suppose I could try manually building Magic into the original boot.img with adb root, but that seems like a quick way to brick the device again.
[Magisk] pndwal:
You could experiment if confident / confirmed stock boot.img can easily be flashed to recover after incompatible boot.img type brick... PW
[Magisk] moocow1452:
I've been able to recover it so far. Is there a guide to manually patching through ADB on the device?
[Magisk] pndwal:
This I don't know... (Likely easier off device with Magisk Tools, AIK etc however.) I think restoring boot.img is only possible thru Fastboot (except on Sammy etc). @ipdev? 😜 PW
[Magisk] zgfg:
Two comments to be accurate:

1) magiskboot is installed by Magisk to /data/adb/magisk, hence it can be called as above:

./magiskboot

only from that folder

It's also not in the path, hence from anywhere else must be called with the full path - as @ipdev stated earlier:

/data/adb/magisk/magiskboot

2) For the actions, one can use unpack or --unpack as well as repack or --repack

Magiskboot help describes that actions should be used as unpack, repack, etc (without dashes), but in fact they work with double dashes or without

However, thanks, the point in your post was that I had to use repack only upon unpack, hence e.g. for boot.img:

su

/data/adb/magisk/magiskboot unpack boot.img

/data/adb/magisk/magiskboot repack boot.img
[Magisk] ipdev:
That is a good step. :)

Now we know it has nothing to do with a repacked image. ;)

In a previous post, you were able to boot a magisk-patched image but, root was N/A.

Now that you can use magiskboot.

Apply the hexpatch you want to try to that Magisk patched boot image and see if it boots. 👀

Cheers. :cowboy:
[Magisk] ipdev:
There was.

Since Magisk v14.0, you have been able to patch boot images with the Magisk app.

So the ADB steps were no longer needed. ;)

Magisk - The Magic Mask for Android - xdaThread - Link​

Cheers. :cowboy:
[Magisk] zgfg:
Magisk Custom 7ca8dc7f (23014) released, both to TG and Github

Dirty flashed over the previous Custom 23013, everything looks ok

Now only (debug) apk file is relesed (to be remamed to zip for TWRP flashing) - for previous versions he had separate apk and zip builds

Fixed download and installation of modules from Repo (there was a problem in Custom 23013).

Still MagiskHide with or without Zygisk (no DenyList).

Otherwise in sync with Canary 23014
[Magisk] ipdev:
Hi all. :D

I do not use twitter so, I am out of the loop at times. :confused:

Links to a few tweets were noted in an issue on USNF github earlier today.

Seemed to be appropriate to mention here.

From John Wu.

From osm0sis

Spoiler content hidden.

Cheers all. :cowboy:
[Magisk] pndwal:
FWIW, more complete thread from @osm0sis twitter since there was more... (Sorry you may need to search, some of us have been warned by mods re. giving links to Twitter, Telegram etc XDA deems 'social media'. We can quote however.):

PW
[Magisk] pndwal:
...And earlier post with John's (very relavent) initial observations:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85824293 PW
[Magisk] pheraspu:
Hello. Just a question. I am using a device (Galaxy A6+) with 32 bits, and I can not use the current canary version. Will next stable magisk version support 32 bit or only 64 bits?

Thanks a lot
[Magisk] Werve:
Hi,

Since I accidentally tipped knox of Samsung Note Pro 12.2 (p905) I tried to change from Supersu to Magisk. I uninstalled Supersu and started installing various versions of magisk from TWRP 3. But the 20.3+ versions fail due to "insufficent partition size". I attach the reovery log of the magisk v20.4 installation and the original boot image and the one modified with magisk v23.

If there are no errors, how can I resize the boot partition without losing the data in the other partitions? Thanks.
[Magisk] m0han:
yeah. and, the 'init.rc modifications' annoyance in magisk detector app is gone too.
[Magisk] rodken:
I too have choosen not to dwell on Twitter and still able to stay 'somewhat' within the loop of foolishness. By the same token I try to avoid 'Novel Information Addiction' which is what social media can sometimes rear it's ugly head at times.
[Magisk] pogo-airsupport:
32 bit support is being dropped.
[Magisk] m0han:
quoting my post to say i had added app_zygote_magic config also to riru-momohider. not sure if it was this that removed the 'init.rc modifications' annoyance or (the new) MagiskCustom 7ca8dc7f (23014) itself. @TheHitMan
[Magisk] z1022:
Where can I download "MagiskCustom" ? Thanks
[Magisk] zgfg:
GitHub - TheHitMan7/Magisk-Files: Magisk File Host

Magisk File Host. Contribute to TheHitMan7/Magisk-Files development by creating an account on GitHub.

github.com

Open and find the Download.

Better, find their the URLs to his TG channels (one for discussion, the other for releases)

Currently, Github is in sync with TG but usually releases on TG go faster
[Magisk] z1022:
And what is the difference with Magisk alpha ?. Thanks again
[Magisk] zgfg:
It has been discussed a lot here. Please read before asking

In very short, In Custom you have only MagiskHide (with or without Zygisk) and the old Magisk Modules repository
[Magisk] z1022:
I have already read the discussion from Oct to now and I still have a litter bit confuse. After I install this two app, I have a litter understand the difference.

Thanks
[Magisk] dr.ketan:
Both version (Magisk (kernel part) & Installed(App)) should match. Update kernel part and it should ask once only.
[Magisk] m0han:
suggest that you stick to just one; either alpha or custom, the latter if you want MagiskHide (with or without Zygisk) and the old Magisk Modules repository.
[Magisk] z1022:
Thank you for your suggestion.
[Magisk] pndwal:
Universal SafetyNet Fix modules v2.2.0 (Zygisk) + v2.1.2 (Riru) are now public!

👍 PW
[Magisk] Eng.Raman:
Fix the detection of "ART parameters are abnormal" in Momo 4.0.1.

The detection of ( ART parameters are abnormal ) known to be caused by LSPosed.

Installing LSPosed will change one of the ART runtime properties in system.prop ( dalvik.vm.dex2oat-flags ) to be fully functional for all the modules.

I figured out a trick how to bypass this detection ( May not work for all your modules ).

1. Use any file manager with root excess and navigate to ( /data/adb/modules/riru_lsposed/ ).

2. Open system.prop there and add # to the beginning of the line "dalvik.vm.dex2oat-flags=--inline-max-code-units=0" then save changes and reboot to take effect.

3. After reboot you will see LSPosed ( Partially activated ) and a warning message "System prop incorrect" ( Just ignore it ).

4. Repeat the steps every time you flash an updated release of lsposed zip in magisk manager.

LSPosed with partially activated is just enough for daily use ( worked well for all my 11 lsposed modules).

Alternative: You can also bypass this detection by disabling the lsposed module in the magisk manager.

Cheers, (y)
[Magisk] Fif_:
That's neat for evading detection but will likely break some LSPosed functionality.

Worse, you won't notice immediately.

Android keeps optimizing applications all the time and recompiles parts of the app code depending on how you use the app.

By turning off this flag, you are preventing LSPosed modules from hooking inline methods. As apps get optimized, LSPosed modules hooking inline methods will start misbehaving.
[Magisk] Eng.Raman:
I know all that. As i mentioned all my 11 modules working well and full funcional with no lag anymore, also i mentioned may not work for all modules you have.

You can try it yourself with your modules and test which modules not properly worked.
[Magisk] vandyman:
With the newest way of using Magisk Canary 23014 and safetynet 2.2.0.

Safeynet passes and Google Pay works.

With that said and out of the way. I have a few apps that will not work with the current setup. They are detecting a safeynet fault of some sort. I am thinking that it is because of the bootloader being unlocked.

I tried with and without the deny list.

Name of the app that I am having trouble with is healow.

Here is a screen shot of the Pixel 6 passing the safety net.
[Magisk] vandyman:
My above issue is working now.

Magisk has to be Hiden.

(had a brain fart). Lol.
[Magisk] sakis_the_fraud:
heeeeey!

old magisk user, it was working like a charm on my galaxy s20, but lately something broke!

I have installed Magisk version 97b72a59 (20419)

and magisk manager version 8.0.7 (4834)

When I open an app that requires root access, nothing happens, and after a while, i get the toast message that denied superuser rights.

i have seen that it happens a lot, but there isn't any solution on these threads!

any suggestions?

thank you in advance for your help!
[Magisk] z1022:
How to setting in Magisk and only safetynet 2.2.0. you installed ?

Which app in deny list ?

Thanks
[Magisk] pndwal:
🤔 Why do you think that? PW
[Magisk] paul_cherma:
Universal safety net fix takes care of the deny list for the google apps/services. You can then add to deny list the apps that you want to hide yourself
[Magisk] vandyman:
Because of Windows 11? 😂😏

It is easier to write the code for just the 64. Adding the 32 is more work and more code. With the lesser code; file size,less errors, and smoother runtime.
[Magisk] pndwal:
I doubt you need worry about losing 32bit support for pretty much any software solution for Android for many years, much less TJW's Magisk which still supports Android 5.0! (That was very beginning of 64bit compatibility.)

Arm will continue to provide smartphone CPU cores with 32bit compatibility mode till 2023...

Magisk package has included both 32bit and 64 bit libraries since... forever... 😛 PW
[Magisk] ipdev:
I am guessing the second note in the canary release notes is the confusion.

[General] Support 64-bit only systems

Little further down is noted.

[MagiskBoot] Support patching 32-bit kernel zImages

Magisk 23014 is working fine on my Nexus 7 (2013) and Nexus 10.

Have a few of each and they are normally running some form of LineageOS.

(Currently 18.1 on flo/deb. 16.0 and 17.1 on manta.) 🙃

Cheers. :cowboy:
[Magisk] z1022:
Android 12

using Magisk Canary 23014 and safetynet 2.2.0. hidden Magisk App , add google play store/services in deny list.

still cannot pass Safeynet
[Magisk] martyfender:
Please explain what Windows 11 has to do with it.
[Magisk] vandyman:
I guess the sarcasm emoji did not show up on your end. No harm meant, just a little humor.
[Magisk] vandyman:
Remove the store/services from the deny list. (unchecked)
[Magisk] z1022:
Magisk Canary 23014 and safetynet 2.2.0. hide the Magisk App

Enable Zygisk

Enforce DenyList

No store/services in the deny list

Reboot

Still no luck pass CTS.

Anyway, thank you for your help
[Magisk] vandyman:
The only other things to try,

Clear cache in the store/services.

Use the config props module.
[Magisk] z1022:
will try.

Thanks
[Magisk] paul_cherma:
when you run the Safety Net Checker what are you failing ?
[Magisk] pndwal:
Please say if you have uncertified ROM, ie custom ROM that doesn't spoof certified (official LOS and many others) or China region stock etc. (Give ROM / device details).

To clarify, if uncertified you will need Magisk Hide Props Config with a certified fingerprint configured specifically (only this) in addition to USNF to pass cts profile match. PW
[Magisk] z1022:
CTS fail
[Magisk] z1022:
before that I use official LOS 18 and Magisk. I can pass safetynet cts and do not need Magisk hide Props Config.

Anyway, thank you for your help
[Magisk] pndwal:
Are you still on Official LOS?

@ipdev noted recently that while they may build with original fingerprint (so it may pass), they don't later adjust dates to match security patches at which point ctsProfile will fail and you will need to configure a certified one with MHPC etc...

Their policy is the reason for this, as well as why they will never integrate safetynet fix solutions either. PW
[Magisk] z1022:
Sorry for my mistake. I use unoffice LOS 18 build, I can pass ctsProfile. I still cannot pass CTS for aosp 12.
[Magisk] pndwal:
mmm.

Guess you mean users could be reading "Only support 64-bit systems" instead of "Support 64-bit-only systems" 🤪

To be clear for those who may have misunderstood, this is referring to vvb2060's fix for "Pure 64 bit"

https://github.com/topjohnwu/Magisk/commit/66cc9bc545585c5d6e5833fdb55964c9b0385f43

Of course, this increases compatibliy (doesn't decrease it)!

Likewise, chaosmaster's "Add support for legacy ARM32 zImage" only broadens compatibility, and in this case for many older and some new (often low RAM & 'go') 32 bit devices.

https://github.com/topjohnwu/Magisk/commit/f41575d8b047e7bb32dfa619df12634eaecc3feb

Yup, yup! 😜 PW
[Magisk] pndwal:
Unofficial LOS builds often spoof.

Guess you mean some custom AOSP build. I'd simply try with a certified fingerprint... PW
[Magisk] quyleanh:
I install MHPC, and try some options but still does not work. Could you please give more detail?
[Magisk] pndwal:
You only need to select a fingerprint option. Choose same or similar model.

Did you try to set it up using interface in a terminal emulator? Please check the readme.md for Magisk Hide Props Config if you didn't get that far. 😛 PW
[Magisk] Randomginger:
Thanks to all those who put the required information in this thread to get our modded and rooted devices working like new again. Fully updated Magisk with USNF2.2 and I can use all banking apps, Gpay and others on my Lineage'd up Razer Phone!

I thought Topjohn Wu's Google job might have made it it impossible to use my phone as a daily, but no, the community is as awesome as ever!
[Magisk] vibrantliker:
How do I unhide magisk? I unnecessarily hid it and didn't really need to.

Currently on 23014 (22)
[Magisk] zgfg:
Magisk app is different thing from Magisk

Do you want to unide Magisk app?

You had to give it a new mame (default is Settings) - find that app in Settings, Apps, open, go to its Settings page and take Restore Magisk app.

For the old v20 it was Magisk mngr and probably different name by default when hiding.- you should have remembered the name you gave/clicked ok (search through all apps in Settings, Apps or App drawer to find it)
[Magisk] Denny@83:
Hi, I'm on Magisk canary 230014; enabled zygysk, installed MagiskHide props config+ Zygisk Lsposed and acivated module: HideMyApplist. I installe safetynet fix 2.2.0

everythings works fine and if I boot phone and do a SafetyNet check, control passes

I have a problem:

if I use Zantiscan or KaliNetHunter (starting Kalichroot), and then (after closing the apps) do a Safetynet Check; control don't pass and Yasnac says to restore the factory ROM.

if I reboot again, everything is ok and safetynet control passes.....
[Magisk] 73sydney:
Dont run Zantiscan or KaliNetHunter, or if you do, do a reboot afterwards

That will be $5 thanks i take all major credit cards

Easiest money ive made all day...i love it when people self diagnose and all i have to do it repost their own words :)

Or try hiding those apps from root detection, though unlikely given what they are

Your post is analogous to posting "ive got this wood over here, and when i just leave it be, its just wood, but when i pour petrol on it and light a match its no longer just wood".
[Magisk] vibrantliker:
DUH (to myself) why didn't I see that?