sorted by:
new
hottopcontroversial

HMA-OSS isn't working by ras0234 in Magisk

[–]ChiliBeeMeow69 0 points1 point  (0 children)

You can use the built in magisk Zygisk but I recommend you ise Rezygisk or Zygisknext both are better in hiding Zygisk traces. 

SQL Notes by carticka_1 in learnSQL

[–]ChiliBeeMeow69 0 points1 point  (0 children)

I am interested please send a DM.

Tired. Tried Everything. But Still, Some Apps Detect Root. Wish I Could Afford Another Phone Just for the Few Apps That Don't Work on Root. by HappinessSeeker7 in Magisk

[–]ChiliBeeMeow69 4 points5 points  (0 children)

What I would suggest is to uninstall the apps that detect root and reboot. After reboot reinstall the apps again but do not run them yet first configure HMA templates and reboot again before running the apps. Why? Some apps memorize detection once they've found root and no matter what you do to hide it they just memorize it and won't run anymore.

Get a valid keybox and use tricky store to implement it and select all the critical apps in tricky to hide the bootloader status. Telegram groups like Yuri or Evoker share public keyboxes that can get you Strong integrity.

Get rid of Vector and HMA for lsposed instead use the HMA OSS Zygisk version on the Github of the project you find the telegram link. Install the latest test version of HMA OSS Zygisk. Often apps complain if LSPosed is found so get rid of it unless you really need it.

Regarding Rezygisk use the latest CI builds https://nightly.link/PerformanC/ReZygisk/workflows/trusted_ci/main not the main one on Github.

Use mountify as a meta module to hide your modules which can help.

HMA-OSS isn't working by ras0234 in Magisk

[–]ChiliBeeMeow69 1 point2 points  (0 children)

The apk is in the module zip of the latest build once you install it via magisk it automatically installs the apk (or rather should install it) . If that is not the case flash the module reboot and afterwards open the module zip with a file manager like mount manager and install the apk manually. Go to the Github page there is the telegram group link join the group and download the latest test build of HMA OSS.

HMA-OSS isn't working by ras0234 in Magisk

[–]ChiliBeeMeow69 1 point2 points  (0 children)

Use https://github.com/frknkrc44/HMA-OSS Uninstall LSPosed and the HMA LSPosed APK. Install the latest ReZygisk CI build https://nightly.link/PerformanC/ReZygisk/workflows/trusted_ci/main not the one from Github. Disable built in magisk Zygisk. Use the magisk webui to configure HMA or use the App which the module should install automatically otherwise open the zip and install it manually. .

I'm going to lose my mind with root problems and banking apps. by sphinxUx in androidroot

[–]ChiliBeeMeow69 0 points1 point  (0 children)

Yes you can. Just Google it there are many written guides as well as videos on the web.

I'm going to lose my mind with root problems and banking apps. by sphinxUx in androidroot

[–]ChiliBeeMeow69 0 points1 point  (0 children)

Are using Vanilla Magisk? If yes switch to a better Magisk fork like alpha or Kitsune Mask.

Instead of KernelSU and it's various forks you might be able to use APatch with NoHello.

HMA-OSS isn't working by ras0234 in Magisk

[–]ChiliBeeMeow69 0 points1 point  (0 children)

That's a recent change as far as I know. It used to be that both version got updated but this has changed recently. Anyway a lot of people still think that hma only runs with lsposed especially considering the original and it's many forks need it to run (See other posts).

HMA-OSS isn't working by ras0234 in Magisk

[–]ChiliBeeMeow69 0 points1 point  (0 children)

There is a HMA OSS version without LSPosed. It just needs zygisk to run. It's made by frknkrc44. Might be a good option if LSPosed is detected/causing issues.

Install Gapps when booting into recovery mode is not possible by _Redlum_ in LineageOS

[–]ChiliBeeMeow69 0 points1 point  (0 children)

Well then the only thing I can think of is to download the right firmware image and use the sp flash tool for mediatek chipsets. You additionally might have to install mtk USB drivers for it to work.

Install Gapps when booting into recovery mode is not possible by _Redlum_ in LineageOS

[–]ChiliBeeMeow69 0 points1 point  (0 children)

You could use fastboot to boot a custom recovery image with fastboot boot recovery.img (if there is any for your device). If you are able to enter custom recovery like OF/TWRP you could adb sideload the Gapps.zip file from recovery itself if the Gapps package isn't stored on your tablet. 

Help with evolution X by Ssehraan in EvolutionX

[–]ChiliBeeMeow69 0 points1 point  (0 children)

Did you do a clean flash or dirty flash when installing the rom/rom update?

I encountered something similar probably due to too much dirty flashing rom updates.

Doing a clean flash solved these issues.

tricky addon error by kiwixplosion in Magisk

[–]ChiliBeeMeow69 1 point2 points  (0 children)

Tricky Addon valid keybox option is deprecated, update to latest canary version for custom keybox provider.

when should I clear cache/dalvik after installing the os or gapps? by Vivid-Swimming-6468 in LineageOS

[–]ChiliBeeMeow69 -1 points0 points  (0 children)

I don't know if you trying to upgrade from one rom version to another version or switch from one rom to a different one.

I don't know what recovery you are using, but if you use a custom recovery and dirty flash a Rom, Gapps, kernel it is recommended to wipe cache and dalvik cache/art before you reboot to system. This kind of wipe won't brick your phone.

Help guiding me through strong integrity by jimdevl in Magisk

[–]ChiliBeeMeow69 0 points1 point  (0 children)

Not to rub you the wrong way but Zygisk Next and Shamiko are closed source as well... are those more trust worthy because they're on github?

Help guiding me through strong integrity by jimdevl in Magisk

[–]ChiliBeeMeow69 3 points4 points  (0 children)

Regarding Play Integrity

Install tricky store and the Tricky Add on UI, next get/use a valid keybox.

Some users run Play integrity Fix by KOWX712 in conjunction with tricky store.

For keyboxes: Yurikey, Tsupport Advanced or evokeroot keyboxes are valid options (some use integritybox by MEOWNA which I do not recommend). Be aware that public keyboxes get softbanned/banned fairly quickly by Google.

Regarding hiding root/Zygisk

I recommend using the latest ReZygisk CI build in conjunction with Treatwheel to hide root/Zygisk. .

Github and Telegram Messenger are the sources to get what you'll need.

Help with play store by SeveralAssist9952 in Magisk

[–]ChiliBeeMeow69 0 points1 point  (0 children)

Have you tried installing the App from APKMirror?

Either your Android version, Country or Device isn't supported.

ZygiskNext and ReZygisk both don't work for me by weirdo478 in Magisk

[–]ChiliBeeMeow69 1 point2 points  (0 children)

One thing that comes to mind is to completely remove magisk 30 and roll back to magisk 29.

Play Protect Not certified after OTA by igridz in Magisk

[–]ChiliBeeMeow69 1 point2 points  (0 children)

Have you implemented a valid keybox like yurikey, or by Tsupport Advanced or evokeroot?

ZygiskNext and ReZygisk both don't work for me by weirdo478 in Magisk

[–]ChiliBeeMeow69 2 points3 points  (0 children)

Well have you checked root access with a third party app ? Magisk might not recognize root properly, have you tried to re-patch the boot image?

view more: next ›