cookie

We use cookies to improve your browsing experience. By clicking «Accept all», you agree to the use of cookies.

avatar

About Me⚡💯 CheatNinja(fromerly sharpshooter) | Cheat | call of duty mobile | PUBG | Hacks | Buy and Sell all games|

«بِسْمِ اللهِ الرَّحْمَنِ الرَّحِیمِ» 🇮🇷تابع قوانین جمهوری اسلامی🇮🇷 Hello.. TELEGRAM CHANNEL: @CheatNinja_TGs_Office Resellership and management :- @ileadershipi Information:- InfoAbout_me ★All Hacks 100%✓ Main ID Safe

Show more
Iran180 442The language is not specifiedTechnologies & Applications
Advertising posts
303
Subscribers
No data24 hours
+107 days
+4230 days

Data loading in progress...

Subscriber growth rate

Data loading in progress...

For custom ROM try this: C6 bank is detecting the 99-magisk.sh file in system/addon.d Just rename or delete it using a file manager with root access, mind you removing it will result in you having to manually reinstall Magisk on ROM updates Either way, there is no 99-magisk.sh file in system/addon.d I only see 30-gapps.sh and 50-lineage.sh, which are definitely giving out custom ROM but at that point I guess addon.d itself is already a red flag for the app.
Show all...
3 2 1
Momo Guide for dummies ✨ ✨.                       &                   ✨ ✨  General recommendations✨  Magisk/Kitsune/KernelSU  ✨ Momo is an app to detect modifications on your system, is more helpful for devs than for normal users, even so, if you want to check your "Momo" due to boredom or your uncontrolled OCD, here's a few quick fixes that are most common, also some tips: - #Magisk_Found: Magisk almost always will be found, unless you use Shamiko or use enforceSuList[1] - #Data_not_encrypted: Your phone isn't encrypted, you can change that easily going to your settings and searching for the encrypt setting. - #Found_files_modified_by_magisk_modules/found executable file "su"/found suspicious files like magisk or TWRP: Just use Shamiko or switch to Magisk Alpha, or KernelSU - #TEE_Broken: Since you unlocked your bootloader the Integrity Chip of your CPU is broken, the fuse, it won't affect usage, few apps detect bootloader. - #Zygote_is_injected/found code injection: You used a lsposed module on Momo, don't do it. - #Bootloader_Unlocked: Self explanatory, you unlocked your bootloader to root and etc. You won't get pass this on Momo unless you use Bootloader spoofer, it doesn't matter, doing so will trigger Zygisk detection on Momo - Fix init.rc/ART and Recovery/Magisk detections - Fix Suspected Mount Detection -Fix ART termux —> su —> setenforce 1 1* Be careful if you enable enforce SuList on Magisk, if you already have some modules it may cause a soft brick, if you soft bricked, try to boot into safe mode. If you really want to fix Momo because some banking apps or games don't work: • Use LSposed no logs (usually not needed when using Shamiko) • Use HideMyApplist module if needed • Install Shamiko • Switch to KernelSU, if needed, install ZygiskNext and Shamiko Also, DON'T use Momo as a test if your phone is be able to open apps, Momo isn't a reliable way to test that, some people run their banking apps with a shitty Momo analysis, others can't open theirs even when Momo shows a clean analysis. There isn't a need to fix Momo or pass everything. Tips: • NEVER NEVER inject Lsposed modules on Momo, never add momo to denylist on Magisk • What Momo sees isn't what each of your apps see, some just search for root, some just search for Zygisk, and a few search for a lot of stuff. • Don't take the results and run with them, you may get a clean Momo and fail to run BPI/Livin' Merchant/Onepay, you may also get a "bad" result and open those apps. 🎉Basic practices to pass apps that won't open on your phone🎉 • Use Magisk Canary or any other flavor of your liking of Magisk as long as it has denylist, enforceSuList, and maybe MagiskHide • Use KernelSU, which out of the box hides everything better than Magisk • Use Shamiko if your root manager allows it → KernelSU/Magisk (experience may vary) • Enable enforce SuList and allow root only on your apps that need it • Don't bootloader spoof on Google services neither Google apps • Don't automatically use HideMyApplist or Bootloader spoofer on an app if you aren't secure it really searches for it. Using a module in an app that you don't know what it does is like going to a police officer and screaming: I TOTALLY HAVENT DONE ANYTHING WRONG, NOPE, I'M JUST CHILLING HERE, LIKE A GOOD PERSON Common recommendation if you have troubles opening apps detecting modifications: • Use KernelSU/KSU + Shamiko + ZygistNext, you will pass everything and open every app without hassle #Links: KernelSU (currently archived) KernelSU fork Magisk Official Magisk Alpha Magisk Delta/Kitsune Mask Shamiko LSposed LSposed-NoLogs [USE AT YOUR OWN RISK] Archived/Deprecated DOESN'T MEAN it won't work anymore
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns before modding. YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Show all...
About Me⚡💯 CheatNinja(fromerly sharpshooter) | Cheat | call of duty mobile | PUBG | Hacks | Buy and Sell all games|

Fix init.rc/ART and Recovery/Magisk detections 1) Search for (/system/addon.d) and rename it. 2) Search for (/sdcard/TWRP) and rename it (Or your recovery name). 3) Search for (/vendor/bin/install-recovery.sh) and (/system/bin/install-recovery.sh) and rename it. Notes: Before dirty updating your ROM rename those files and folders back to the original state. Init.rc might also be due to (/vendor/etc/init) which are prebuilt into your ROM by default. Credit to HuskyDG and all the people in his group who help and share knowledge.

3 1 1
UI issue has been fixed now, if you had empty details, this fixes it.
Show all...
4 2👾 1 1
Fix Suspect Mount Detected (root detection) 1) Use MemoryDetector & Native Root Detector to know which modules are mounted to the system. 2) Flash magical_overlayfs 3) Change (/data/adb/modules/magisk_overlayfs/mode.sh) to  (OVERLAY_MODE=2) 4) Now comes the dynamically loading detected modules using overlayfs image, Edit your detected modules (/META-INF/com/google/android/update-binary) and add the following script before the exit. 5) Reflash the module and check MemoryDetector. 6) Do for all detected/mounted modules.
OVERLAY_IMAGE_EXTRA=0     # number of kb need to be added to overlay.img
OVERLAY_IMAGE_SHRINK=true # shrink overlay.img or not?

# Only use OverlayFS if Magisk_OverlayFS is installed
if [ -f "/data/adb/modules/magisk_overlayfs/util_functions.sh" ] && \
    /data/adb/modules/magisk_overlayfs/overlayfs_system --test; then
  ui_print "- Add support for overlayfs"
  . /data/adb/modules/magisk_overlayfs/util_functions.sh
  support_overlayfs && rm -rf "$MODPATH"/system
fi
Fix Revanced mount detection: 1) Download & Flash Zygisk Proc Injection 2) Download YT Revanced Inject 3) Download & Install stock YT matching the inject version. 4) Flash YT Revanced Injection module. 5) Reboot and check if detected now. How to update YT Revanced? 1) Change the module.prop (version=) in the Injector module so it matches your YT version. 2) Replace revanced.apk within your new Revanced APK within YT Injector module. 3) Installed version must be stock and match revanced.apk version. 4) Flash YT Injector and enjoy. Notes: YT Revanced Injector could in theory be used and modified to work with other Revanced mods. If you use Revancify execute it with the parameter -n (rootless) to build the APK and not install it automatically. If you still have the suspicious mount detected it must mean that your /data partition type is not f2fs. (su -c stat -f -c %T /data) Credit to HuskyDG and all the people in his group who help and share knowledge.
Show all...
Tesla in Pixelify Support Group

3 1 1
Fix init.rc/ART and Recovery/Magisk detections 1) Search for (/system/addon.d) and rename it. 2) Search for (/sdcard/TWRP) and rename it (Or your recovery name). 3) Search for (/vendor/bin/install-recovery.sh) and (/system/bin/install-recovery.sh) and rename it. Notes: Before dirty updating your ROM rename those files and folders back to the original state. Init.rc might also be due to (/vendor/etc/init) which are prebuilt into your ROM by default. Credit to HuskyDG and all the people in his group who help and share knowledge.
Show all...
3 1 1
Photo unavailableShow in Telegram
ممکن گیم پلیرا از اینکه گوشیشون داغ میکنه و fps پایین میاد ناراحت هستن من یه موبایل رادیاتور کولینگ فراهم کردم که خودم ازش استفاده میکنم و واقعا راضیم و حواب میده انگاری گوشیت تو یخچال به زودی موجود میکنیم با پایین ترین قیمت مدل های بهترش هم عکس براتون فراهم میکنم اگه خوشتون اومد بخرید من از این راضی بودم مشکلی هم نداشت
Show all...
5 2 1