ЯevDex

RePairip is almost done 👍 now library surgery is super smart

i want some advice from you guys 😐 i was working on an advanced file manager called hm manager which is basically an alternative to mt manager but suddenly i stopped working on the project because i noticed that google is adding a lot of restrictions around sideloading and apk installation now my question is after putting so much effort into building this tool what if people can't actually use it in the future? then all my hard work on hm manager would basically become a miracle project that nobody can properly use 🥲 the main purpose of hm manager is to do things like dex editing apk modification signature killing etc but if someone modifies an apk using my tool and then tries to install it and they start getting restrictions like having to wait 24 hours or facing other installation limitations then what's the point of my tool? after thinking about this a lot i've decided to pause the development for now i'm waiting to see what google does with the upcoming updates and how these restrictions actually work after that i'll decide whether i should continue working on hm manager or not if anyone knows more about this or has any information about google's upcoming changes and how they might affect apk modification and installation please share your thoughts in the comments i'd really appreciate your opinions 🙏

MuMuNxMain_patched.exe

https://github.com/ispointer/RePairip.git New Update is dropping soon

I wasted 8 fucking hours cracking DFT Pro tools but I finally fucking succeeded 😂

my 1 device is gone 🥲 the fucking preloader BIOS is completely gone after I tried to patch it fuck it I never give up let’s try again

https://t.me/MemDebugger/73 https://t.me/MemDebugger/73 https://t.me/MemDebugger/73

assembly-csharp.patch.bytes loader for developers 😂😂 a lot of big game companies use systems like this. basically, imagine they find a bug inside one function of the game. just to fix that one function, they don't want to update the whole libil2cpp.so and release another huge game update. so instead, they use a byte patch loader. they compile only the target function's fixed code, make a small patch payload like assembly-csharp.patch.bytes, and push it to the user side. then the loader already inside the game loads that patch and applies the fix. pretty cool idea, right? 😂😂 but the funny part is, some modders are abusing the same concept. if they find a game with this kind of patch loader and manage to use it, they can make their own custom .patch.bytes containing modified game logic and load it into the game. so basically they can change some game functions through the patch system without directly modifying the original apk 😂😂 i saw a project like this today and thought the whole concept was really interesting, so i wanted to let you guys know about it.