android persistent threat
@ptrpaws3.8K followers
155,949 views
40 Comments
Comments from the original post on X (Twitter)

@ptrpaws
don't worry about it kitten
95 likes

@Tarek724375
Did you have to add that shitty dubstep music?
52 likes

@ptrpaws
yes
42 likes

@kebabenseLSS
Is this just dirty flag running on boot?
17 likes

@ptrpaws
no. every bug involved was found by me
36 likes

@GashbinO68368
Using AI to find this vulnerability doesn't mean you discovered anything special or did it yourself. Anyone could do what you've done if they had the money or access to this model.
14 likes

@ptrpaws
what
164 likes

@GashbinO68368
Did you use AI or not?
2 likes

@fred6279
Does this fail on Graphene?
11 likes

@ptrpaws
yes. graphene has appropriate mitigations that prevents exploitation
127 likes

@laurameow161
show if your bootloader is locked with factory keys
10 likes

@denay39th
using pixel without graphene is crime towards humanity
5 likes

@_m0ab
so what are the chances of a root releasing that doesn't fuck with Google play api
4 likes

@dialga1453
is this more convenient for modules than the dirtyfrag method??? i assume the bootloader is locked tho
3 likes

@mesosan16
sus. CVE please?
3 likes

@GenevivePhiPhi
Up to date but it's Android 15 It's because you need a specific range of stock models and/or a specific range of stock kernels that have the exploitable CVE's
2 likes

@fedcoiner
You're a man nigga, admit it
2 likes

@tsisartbysekai
tryna pull a calif on us
2 likes

@lonelytransgrl8
>uses stock android on a pixel ?????
1 like

@xexif49197
mentally ill activities right here, go find a job you f*g
1 like















