I found another module that bricks your phone permanently.

However, it looks like a traditional module, but all of its contents are encrypted like this. (This is an example code snippet, and there was a huge code around 1500 characters.)

eval "$PDO$BNg$sVM$ubq$rlM$BNg$VuZ$ubq$BAl$uze$Ylg$wvm$BAl$eHk$FQo$Nse$ymc$LuZ$BAl$PDO$BNg$sVM$....."

Don't install any module other than official sources, and don't even install any modules from unofficial sources claiming this gives you 169+ fps, etc.

You have been warned.

Always check the .sh files inside in your modules to confirm what's actually going on.

@APatchChannel.

The first three lines of that code says :

Happy New Year
Have a happy new year
The first brick of the new year

Then it starts to flash zero to all of your partitions..🧱

There's a problem with some terminal commands in APatch.

But don't worry! Here's a simple and temporary fix for it.

You'll need : Shizuku, Termux.

Procedure :

01. Open APatch and grant Shizuku root permissions.
02. Open Shizuku > tap on "Start".
03. Now select "Use Shizuku in terminal apps".
04. Choose "Export files" > save them to your storage.
05. Open Termux > change the working directory to the saved location.
06. Run the command bash rish and grant Shizuku permission.
07. That's it! You're done.

* Just a reminder, this is only a temporary solution. We're working to fix the issue in future updates.

@APatchChannel ❤️

#guide #fix

universal guide to convert read only super img to read write ( works only on devices with super imgs )

1. custom recovery pre installed
2. follow the link posted and download latest stable script
3. flash the script through custom recovery
4. choose partion size starting with minimal size / use custom size of your choice
5. debloat rom as per requirement if there's sizing error
6. use decryption if you are okay with data formatting else skip it
7. initiate the process
8. done your system is fully converted to read write

note : tested on erofs system
device : reatoll ( realme7pro )
script author : leegarchat
guide edited by : @kwshl

https://xdaforums.com/t/magisk-twrp-arm32-64-a8-universal-read-only-to-read-write-for-android-ro2rw-auto-converting-super-system-partitions-to-read-write-mode.4521131/

#team_apatch

I just created a simple script to patch the boot image with APatch on Samsung devices.

- This script also disables the Samsung security features in the kernel.

- It might be able to fix bootloop issues on some devices.

- However, it didn't work on my device since it has a newer version of Samsung RKP and Control Flow Protection (CFP).

- You should try patching the boot image yourself; if it succeeds, you are lucky.

- If you know the hex patches for the new RKP and CFP, feel free to contribute..🙂

Here's the repo :

https://github.com/ravindu644/APatch-Samsung

#samsung

Introducing Kitchen (Boot image unpacker and repacker)

Developer: @ravindu644

Description: This script can unpack, repack, and sign the boot images of Android without breaking Android Verified Boot (AVB).

Finally, We can edit our boot images without issues..! 🎉

Documentation

https://github.com/ravindu644/Kitchen

#android #avb #tools #kitchen

A novel malicious module has emerged.

This module advertises itself by concealing the Bootloader unlock status. Once flashed, it renders your phone inoperable.

Do not place trust in anything that completely conceals the bootloader unlock status!

Therefore, before flashing the module, thoroughly inspect its contents to the best of your ability!

We aspire for every individual's mobile device to remain unscathed by such malicious module attacks.

The update has too many changes, and some issues have caused crashes. Let me take a few days off before solving the problems. Of course, feel free to submit pull requests.☺️

New release!

What's Changed

Compat termux's su by @bmax121 in #264

https://github.com/bmax121/APatch/releases/tag/10533

New Release : 10568

What's Changed

- Refactor KernelPatch installation logic and initial support for A/B upgrade after OTA, by @pomelohan and @Admirepowered.
- Introduce Module WebUI feature from ksu.
- Introduce APatch update notifier.

Full Changelog : 10533...10568

@APatchChannel

#release

I just noticed APatchLite, and this is not directed at APatchLite specifically. APatchLite is guaranteed to be safe as it is a version forked by a developer of the APatch app. However, there is an issue: the superkey is embedded in the source code, and it is not advisable to skip the setting of the superkey.

10569

1. Fix find kallsyms_marker error (For example: OnePlus 12 with kernel 6.1.57 and etc)
2. Try to fix module install os error 22 or 5, but not 100% guaranteed.

Due to previous mistakes, both the group and the original management have been disbanded. We are now discussing the combination and merging into the same group, and all management personnel have been changed to developers. We do not want any unpleasant things to happen again and would like to join a new group, https://t.me/apatch_discuss

🎉 New APatch release available 🎉

Upgrade KernelPatch to 0.10.5
Strip busybox so that APatch's size decreased
New refreshed UI
Introduce theme manager and custom dark mode switch
Switch to stable compose dependence release
Fix settings page not scrollable
Enhanced Image flashing operations
Optimize InstallScreen experience
Refine dialog component and add an animation to UpdateCard
Enable blur behind compose dialog for Android S+
Add an alertdialog if failed to auth super key
Refactor Installaction UX&UI
Use lsplugin resopt to optimize apk size
Refine WebUI
Implement KPM Control Feature
Implement isSafeMode detect
Fix extract kpm infomation from boot error
Fix round corner for APModule Info Card
Fix random build signture
Adapt Zygisk Next WebUI
Fix twice try when selecting an invalid boot image
Allow system_server devpts read/write chr_file
Fix unable to configure exclude feature for non-root apps
Now SuperKey are no longer plaintext in the process of transmission and storage
Fix the logic for processing the "UNCOMPRESSED_IMG" header
kptools: Skip relocation when trying again
Fix safemode typo
Import translations changes (By all contributors ❤️)

Note:
This version includes many updates. Please backup important data before installation or upgrade. We are pleased that Zygisk Next has added support for APatch. To be compatible with its whitelist function, we have added an "exclude" setting button. It should be noted that if Zygisk Next is not used, it has no practical significance because we have not yet implemented this feature due to time constraints. It is a known issue that some software cannot obtain ROOT permission, but only a very small number of software have experienced this bug. We are doing our best to solve and develop it. Thank you for your support and understanding.

Report bug or feature request: https://github.com/bmax121/APatch/issues/new/choose

@APatchChannel

🎉 New APatch release 10763 is available 🎉

Changelog
Upgrade KernelPatch to 0.10.7
Upgrade java and rust dependences
Fix compat syscall, 32-bits su command is supported now
Shrink apd size
Remove buggy and redundant hide manager feature
Re-designed About and Module Screen UI, thanks to SanmerDev MRepo's design
Fix os error 2 during installing modules
Switch to new enableEdgeToEdge, drop accompanist/systemuicontroller
Optimize APatch Safe Mode
Fix module online upgrade not working
Re-design exclude modifications feature
Translation imported, thanks to all translators
More optimizations and minor changes

Notes
The newly designed exclusion module modifies the logic, and from now on, applications that have already been granted ROOT permissions no longer support exclusion because it does not conform to the logic of normal usage scenarios; By default, modules will no longer be excluded because not all software will check the current environment, which undoubtedly brings unnecessary power consumption and heat to the phone. You can manually configure the applications that need to be excluded. It should be noted that if you are upgrading from a version of KernelPatch below 0.10.7 instead of a completely new installation, you need to manually delete the /data/adb/ap/package_config file and reconfigure it on the SuperUser screen, otherwise a BUG may be occurred.
We have noticed that some older devices (mainly those with Linux kernel versions less than 5) may experience unlimited loading of SuperUser Screen, and even some applications may not be able to use ROOT permissions. This is a known issue and is currently under investigation.

👉 Report bug or feature request: https://github.com/bmax121/APatch/issues/new/choose
👉 @APatchChannel