Originally Posted by k4y0z
Are you talking about this?
"the zero day exploitation" isn't really a good description.
I was gonna check it out as well, there is a poc available with a write-what-where primitive.
You could probably easily make an mtk-su fork that replaces the mtk-primitive with this one
Yeah, I looked at the code and the memory r/w routines could be fairly interchangeable because this is in the same league as mtk-su. (Are you gunning for temp root on the Fire TV 4K stick?
) But seriously, can you check if Amazon's/MTK kernel has been patched for this? It may only apply to Oreo+ devices though, from what I read.
Originally Posted by rc1421x
My smart-brick (tcl a502dl & 8.1) does not allow "enable background" app option for either MM or init.d support (some other apps still do). So I disabled Battery Optimization for MM & Init.d support & enabled app Notify for both. As for MM I added Autoresponse Grant.
Now after boot the whole shebang is no-go but a init-supp "run scripts now" starts it OK - every time after so many restarts that my smart-brick belongs on my fireplace.
Also I "think" that booting with the USB cable connect to PC is naughty -- I knew you guys hated Windows but sheesh...
I don't get what you're saying here. So it did work with automatic Grant, or not? (And what is booting with USB cable connected?)
Originally Posted by Supermatt01
I mean that the reason it is being patched up is because it's claimed that people are using it for injection of malware. I would hope to use it to our advantage without malware.
Yes, that one. It says that OPPO devices may be vulnerable to the exploit. If it is a kernel issue, maybe it will work on Snapdragon and MTK devices.
There's no such thing as full root without the possibility of malicious actions. I guess that's what you mean by malignancies. A vulnerability that lets you get root access is of the highest severity. That means it's at the highest priority of getting patched. Doesn't matter what's it's already being used for...