If you reboot, aegis will noticed it's not the original binary and it will not work until you replace it again (or chmod maybe).
Just restart whatsup after replacing file
If you reboot, aegis will noticed it's not the original binary and it will not work until you replace it again (or chmod maybe).
Just restart whatsup after replacing file
Oo..is aegis, no wonder the behaviour so weird..let me try replace again..thx cepi..
I spoke too soon..now can't trigger the binary after reboot..promptin 'operation not permitted'...weird bcos binary aredi 777..
Strange, I ran into the same problem. After Whatsup running for almost a week, this morning my phone became very slow, and I noticed Whatsup was using >230MB of RAM (I don't know what is normal, though).
If you reboot, aegis will noticed it's not the original binary and it will not work until you replace it again (or chmod maybe).
Just restart whatsup after replacing file