As I didn't root my device yet, I can't write to /data/misc/rootrecorder
. Moreover, I didn't find any use of this backdoor in the limited part of the firmware I have. I will continue to dig 
-
Show this thread
-
How exactly is this a backdoor then?
1 reply 0 retweets 0 likes -
There 2 possibilities: - Set this flag will root the device - This flag is set after a root procedure As my device is not rooted, I cannot test it for now. Anyway, it's clearly shows that a root procedure had been implemented by
@ARCHOS without the knowledge of the user1 reply 0 retweets 0 likes -
You shouldn't call it a backdoor if you haven't tested that. Plus if it already needs root to write to /data, then so what? That process already has root so what would be the importance of this?
1 reply 0 retweets 0 likes -
A root procedure implemented by the phone maker without the knowledge of the user is a backdoor... Not sure you really understand the thing here. As said in the tweet this is a partial result but it clearly shows that
@ARCHOS has a way to root the device.2 replies 0 retweets 0 likes -
Replying to @fs0c131y @MishaalRahman and
is it a functino to root the device? it sounds more like a tamper flag set when root is detected. Of course OEMs can root devices, they all have a way if they want
1 reply 0 retweets 2 likes -
Replying to @jcase @MishaalRahman and
Yep it sounds like an internal root flag, I just want to check where this flag is set :). Ofc they can. I'm just asking them to remove that in the user build :)
1 reply 0 retweets 0 likes -
Replying to @fs0c131y @MishaalRahman and
not really possible, I mean they control the certificates, OEM can always gain greater privs
1 reply 0 retweets 1 like -
Replying to @jcase @MishaalRahman and
Yes sure, if you signed your app with the platform certificate you can do whatever you want. A good start for OEM will be to remove these "easy root ways".
1 reply 0 retweets 0 likes
You will see what I mean when I will publish what I found on the Blu Vivo 8 :)
-
New conversation
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
debug purposes