I installed shamiko in Apatch with a trick hahaha

[Morrigan-Ship]

in first root via magisk

install zygisk-next and shamiko last version then install Apatch and flash boot made by Apatch now goto modules section in Apatch and Enable shamiko :)

[VisionR1]

But working actually? Because still can install it in APatch, if you know how.

[Morrigan-Ship]

yes root your device with magisk install shamiko now install Apatch install zygisk-next module in Apatch

magisk modules auto install to Apatch from previous magisk

[VisionR1]

Understand, I'm asking, if after all this works. Because can install in APatch if you modify and say work inside, but actually not working.

[Morrigan-Ship]

it show unsupported environment i dont know it working well or not. but i tested it in Kitsune and same error unsupported environment

i think if you update magisk api's it fix the problem i can help you The worst scenario is to edit the Shamiko Source to work, which I am currently helping

[Morrigan-Ship]

can we contact in telegram?

[VisionR1]

it show unsupported environment i dont know it working well or not. but i tested it in Kitsune and same error unsupported environment

i think if you update magisk api's it fix the problem i can help you The worst scenario is to edit the Shamiko Source to work, which I am currently helping

Exactly. Kitsune Mask is not supported from the beginning. I don't know how to this. And shamiko is closed source.

EDIT: I think, you can check with some detectors apps to see if actually works.

[Morrigan-Ship]

momo can find zygisk and magisk it not work

EDIT: But we were able to get one step closer

[VisionR1]

momo can find zygisk and magisk it not work

EDIT: But we were able to get one step closer

Try and other new apps like native test, native root Detector, momo is old. Many users who know at least the basic, have installed but not working, this must be fix it by devs. of shamiko.

[Morrigan-Ship]

i tested native test:

native root detector:

its full result i can see lsposed modules but cannot see magisk

[Morrigan-Ship]

also rootbeer sample not found root or anything

[VisionR1]

Do you have it in exclusion list? Or just shamiko install?

[Morrigan-Ship]

i just installed shamiko

[VisionR1]

Maybe work one part, service.sh. Lot of users take only this.

[Morrigan-Ship]

i checked service.sh it just change some values to hide everything

check_reset_prop "ro.boot.vbmeta.device_state" "locked"
check_reset_prop "ro.boot.verifiedbootstate" "green"
check_reset_prop "ro.boot.flash.locked" "1"
check_reset_prop "ro.boot.veritymode" "enforcing"
check_reset_prop "ro.boot.warranty_bit" "0"
...

if yes can we use this alone? it mean make a custom module? i try now!

[VisionR1]

i checked service.sh it just change some values to hide everything

check_reset_prop "ro.boot.vbmeta.device_state" "locked"
check_reset_prop "ro.boot.verifiedbootstate" "green"
check_reset_prop "ro.boot.flash.locked" "1"
check_reset_prop "ro.boot.veritymode" "enforcing"
check_reset_prop "ro.boot.warranty_bit" "0"
...

if yes can we use this alone? it mean make a custom module? i try now!

Many users, already do that, have a folder service.d or boot.complete.d inside in the adb.

[Morrigan-Ship]

Many users, already do that, have a folder service.d or boot.complete.d inside in the adb

then what is the problem we can use it instead of shamiko

[VisionR1]

Many users, already do that, have a folder service.d or boot.complete.d inside in the adb

then what is the problem we can use it instead of shamiko

Is a simple service.d, just hide the very basic, the full hide is inside in the shamiko code.

[Morrigan-Ship]

i find something :) post-fs-data.sh this file: it checking kernel su and magisk versions:

MAGISK_VERSION="$(magisk -V)"
KSU_VERSION="$(su -V)"

i tested in adb:

adb shell
su
su -V
11039

magisk -V
/system/bin/sh: magisk: inaccessible or not found
magisk binary no in $PATH so it cannot find it :/
so it error:
install new version of magisk 27005

[Morrigan-Ship]

yessssssssss yes yes yesssss i installed it without trick hahaaaaaa

[Morrigan-Ship]

i edited customize.sh and verify.sh and fixed

[Morrigan-Ship]

ops installed but after reboot it show unsupported environment :// can someone give me a shutgon

[VisionR1]

Yeah i know this. That's I'm talking you in my above comments. Users which installed with this way, but after say 'unsupported environment', because the working code is inside in the shamiko source, and is closed source, so we can't do much.

[Morrigan-Ship]

i success to bypass the Unsupported environment i still working on it but i dont know how to sure it realy working or not! i need help

[VisionR1]

i success to bypass the Unsupported environment i still working on it but i dont know how to sure it realy working or not! i need help

How bypass ? 🤔

[Morrigan-Ship]

How bypass

with hark work 😐😂 change all module.prop value easy

[VisionR1]

How bypass

with hark work 😐😂 change all module.prop value easy

That's is good. 👍🏻

[Morrigan-Ship]

grep -nia "magisk" /proc/self/mountinfo
grep -nia "magisk" /proc/self/attr/prev
grep -nia "magisk" /proc/self/attr/current

some apps use these to find and detect zygisk, zygote, magisk may help you

[VisionR1]

grep -nia "magisk" /proc/self/mountinfo
grep -nia "magisk" /proc/self/attr/prev
grep -nia "magisk" /proc/self/attr/current

some apps use these to find and detect zygisk, zygote, magisk may help you

Yeah. Unfortunately lot of parameters can cause the detector, even with shamiko.

[Morrigan-Ship]

but main problem with shamiko is that magisk -V: command not found because magisk is not in $PATH make a new version with magisk in PATH i will test it

[VisionR1]

but main problem with shamiko is that magisk -V: command not found because magisk is not in $PATH make a new version with magisk in PATH i will test it

Understand. Good luck with that. In Kitsune Mask also can't install.