Download Smali Patcher [Magisk Module]

download-smali-patcher-magisk-module

What is Smali Patcher?

To sum things up this is an application I developed that pulls the android framework from your device, applies what I (or other users) consider useful patches to the sourced files and then finally generates a magisk module applying the patches system-lessly.

The unique thing about Smali Patcher is it sources the framework files from your device, in an attempt to provide maximum compatibility across the entire android device family. The project has evolved over time, originating from very humble roots.

My main goal behind this project was to make this thing as user-friendly as possible, considering the circumstances and the hoops I’ve had to jump through I think I’ve done an O.K job at accomplishing that goal.. while I have your attention I wanted to throw out a massive thank you to all the people who have provided support to the project and the thread over the years, you guys are absolute champions. I can’t thank you enough and couldn’t have done it without you, here’s to ya!

CERTAIN PATCHES WILL NOT WORK WITH ANDROID 10, ANDROID 10 SUPPORT IS CONSIDERED ALPHA.. YOU HAVE BEEN WARNED.

PATCHES

  • Mock locations – Hide mock locations status, allowing apps like Pokemon GO to treat them as genuine location updates.
  • Secure flag – Allow screenshots/screensharing in secure apps.
  • Signature verification – Disable signature verification allowing modification/execution of signed system apps.
  • Signature spoofing – Enable signature spoofing app permission.
  • Recovery reboot – Reboot directly back into recovery from the power menu.
  • Samsung Knox – Bypass Samsung Knox trip protection, only confirmed working for secure folder.
  • High volume warning – Disable high volume popup dialog.

GPS SPOOFERS / FUSEDLOCATION / RUBBERBANDING NOTICE

FusedLocation API GPS spoofers are NOT compatible with the mock location patch.. your required to use a traditional GPS spoofer! Spoofed location updates will be fed into fused location, all the same, meaning you don’t need to disable the service.. which means while your not spoofing you still gain the benefit of fused location which is all around more accurate location updates!

REQUIREMENTS

INSTRUCTIONS (ADB METHOD/AUTOMATED – RECOMMENDED)

SMALI PATCHER COMPATIBLE WITH BOTH ODEX & DEODEXED ROMS! WILL AUTOMATICALLY DEODEX REQUIRED FILES IF NECESSARY.

  1. Backup device.. safety first kids.
  2. Enable USB debugging in developer settings on your device and connect via USB to your PC.
  3. Authorise USB debugging connection on your phone.. example of popup.
  4. Run “SmaliPatcher.exe”, First startup will automatically download the latest necessary binary’s.
  5. Select your desired patches.
  6. Hit “ADB PATCH” button (yes without browsing for a .jar file).
  7. Once the process has completed, SMALI PATCHER magisk module will be generated in the same directory as “SmaliPatcher.exe” named: “[email protected]”.
  8. Install the generated magisk module either in recovery mode or from the magisk app.
  9. Enable smali patcher module in magisk manager app.

INSTRUCTIONS (ALTERNATIVE METHOD – FOLLOW ONLY IF ADB METHOD FAILS)

  1. Backup device.
  2. Enable USB debugging in developer settings on your device and connect via USB to your PC.
  3. Authorise USB debugging connection on your phone.. example of the popup.
  4. Run “SmaliPatcher.exe”, First startup will download the latest necessary binary’s.
  5. Browse to your “/system/framework” directory. The easiest way to obtain these files is from your ROM img/zip.
  6. Select your desired patches.
  7. Hit the “PATCH” button.
  8. Once the process has completed, magisk module will be generated in the same directory as “SmaliPatcher.exe”.
  9. Install the generated magisk module either in recovery mode or from the magisk app.
  10. Enable smali patcher module in magisk.

YOU ARE STILL REQUIRED TO HAVE A DEVICE CONNECTED TO YOUR PC IF YOU USE THIS METHOD.. THE PATCHER WILL NOT PROGRESS OTHERWISE.

An ADB DEVICE IS REQUIRED TO EXTRACT CDEX FILES.. IF YOU’RE PARANOID/SAVY ENOUGH, YOU CAN USE A ANDROID EMULATOR.

BEFORE REPORTING ANY ISSUES

  1. You have tried running the patcher as administrator.
  2. You have accepted the USB debugging connection & ticked “Always allow from this computer”.
  3. You have tried running the smali patcher with phone booted in recovery mode with /system mounted.

UPDATING MODULE INSTRUCTIONS

Disable/uninstall any active smali patcher modules before generating a new one! If you generate a module with an older version active there’s a chance the outdated patches will carry over to the new module. I do my best efforts to prevent this, but it may still happen. Before reporting issues, make sure you have tried this.

PRECAUTIONS / TERMS OF USE

You must back up your device prior to flashing the module, I am not responsible or providing support to recover any devices stuck in bootloops.. if for whatever reason you find yourself in this situation, simply uninstall magisk and reinstall.. doing this will reset your installed modules.

PLEASE READ FAQ IN POST 2 & SEARCH THE THREAD BEFORE ASKING QUESTIONS, CHANCES ARE THEY HAVE BEEN ANSWERED ALREADY AND YOU CAN FIND YOUR ANSWER IMMEDIATELY.

Rather than making mirrors of the download link, please redirect traffic to this thread to ensure they are always using the latest version! Oh hi, Reddit.

DOWNLOAD Smali Patcher

Credits

Honourable mention to @Eng.Raman & @A30NI_Y, who has been kind enough to patch service.jar’s for tons of users who lack the knowledge to deodex (despite my best efforts of writing out clear instructions!)… the smali patcher user base thanks you for your service!

FAQ

HELP! I’M STUCK IN A BOOTLOOP, HOW DO I UNINSTALL

  1. Boot into TWRP
  2. Advanced -> File Manager
  3. Navigate to: data -> adb -> modules -> select the module directory (in this case “fomey.smalipatcher”) -> Folder icon (bottom right of screen) -> Delete

Alternatively, you can just uninstall/reinstall magisk to clear all your modules.

MAGISK TEMPLATE DOWNLOAD FAILED

  • Run the patcher as an administrator, may not have read/write access to drive.
  • Verify you have an active internet connection.
  • Verify the firewall is not blocking the patcher.
  • Verify your not running an outdated .NET framework.

MOCK LOCATION RUBBER BANDS TO REAL LOCATION

INVALID OR CORRUPT JAR FILE BIN

  • Delete the “bin” directory and restart the patcher to re-download the binary files.
  • Corruption is caused by a unreliable internet connection.

HOW DO I CLEAR A MOCK LOCATION WHILE USING A GPS SPOOFER

  • Exit the app by pressing the “back” key, you may have to press this a few times. Any good spoofer should clean up after itself, by removing any mock providers on exit.

MAGISK TEMPLATE FAILED TO DOWNLOAD

  • Make sure you’re using the LATEST release of the patcher.
  • If you are using the latest version already.. an update will be available shortly to fix this issue.

UNSUPPORTED MAJOR.MINOR VERSION XX.X

  • Use the Java Uninstall Tool to clean up out-of-date java versions and reinstall the latest java release.

W: COULD NOT FIND RESOURCES

  • This is a harmless warning, you can safely ignore it.

!!! ERROR: BASE DIRECTORY NOT FOUND

  • You did not accept the USB debugging permission popup on your phone.. the patcher can’t do anything without this permission (example of popup).
  • The permission popup should be displayed after hitting the “ADB PATCH” button.. or as soon as you connect your phone to your PC.
  • If you can’t see the permission popup: go to settings -> developer options -> revoke usb debugging authorisations.. disconnect and reconnect your phone and try again.
  • Make sure you tick “always allow from this computer”.. otherwise you may have to confirm the popup multiple times during a single patch.

!!! ERROR: XYZ CLASS NOT FOUND

  • If you are browsing for a services.jar – it’s most likely not deodexed.. try the “ADB METHOD”.
  • If you are using the “ADB METHOD” and you receive this error, post a reply to this thread including as much information as you can. Useful information: android version, patcher log and the directory named “adb” in the smali patcher folder (upload this directory to google drive).
Leave a Reply