Backstory:
As some may have heard, or found out the hard way,
The latest two versions of KingRoot when run on the N910A do something slightly different (or more violently) than previous versions did.
It edits the kernel in a way that causes the device to show "KERNEL IS NOT SEANDROID ENFORCING" in the top left corner during bootup, and from there displays
a screen which reads "System Software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nearest AT&T store for help"
The top-left corner text has at that point changed to "SECURE FAIL: KERNEL"
If I boot into download mode I can reflash the stock image (with Odin) and afterwards it boots properly, all apps and user data left untouched.
Big Questions:
Is it possible that this insecurity of the kernel could be used (even though the phone is left temporarily incapacitated) to flash something a bit.. more than stock firmware?
I don't know in what ways the kernel is changed that makes it just insecure enough to stick that way, but not enough to not engage security features to stop you from booting up completely.
Nobody has been talking about this (as far as I've seen) and I just wanted to hear something from an android expert greater than myself on the subject.
-Galacticboy2009
As some may have heard, or found out the hard way,
The latest two versions of KingRoot when run on the N910A do something slightly different (or more violently) than previous versions did.
It edits the kernel in a way that causes the device to show "KERNEL IS NOT SEANDROID ENFORCING" in the top left corner during bootup, and from there displays
a screen which reads "System Software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nearest AT&T store for help"
The top-left corner text has at that point changed to "SECURE FAIL: KERNEL"
If I boot into download mode I can reflash the stock image (with Odin) and afterwards it boots properly, all apps and user data left untouched.
Big Questions:
Is it possible that this insecurity of the kernel could be used (even though the phone is left temporarily incapacitated) to flash something a bit.. more than stock firmware?
I don't know in what ways the kernel is changed that makes it just insecure enough to stick that way, but not enough to not engage security features to stop you from booting up completely.
Nobody has been talking about this (as far as I've seen) and I just wanted to hear something from an android expert greater than myself on the subject.
-Galacticboy2009
from xda-developers http://ift.tt/1qapo87
via IFTTT
No comments:
Post a Comment