25.xhtml 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159
  1. <?xml version="1.0" encoding="utf-8"?>
  2. <!--
  3. h t t :: / / t /
  4. h t t :: // // t //
  5. h ttttt ttttt ppppp sssss // // y y sssss ttttt //
  6. hhhh t t p p s // // y y s t //
  7. h hh t t ppppp sssss // // yyyyy sssss t //
  8. h h t t p s :: / / y .. s t .. /
  9. h h t t p sssss :: / / yyyyy .. sssss t .. /
  10. <https://y.st./>
  11. Copyright © 2015 Alex Yst <mailto:copyright@y.st>
  12. This program is free software: you can redistribute it and/or modify
  13. it under the terms of the GNU General Public License as published by
  14. the Free Software Foundation, either version 3 of the License, or
  15. (at your option) any later version.
  16. This program is distributed in the hope that it will be useful,
  17. but WITHOUT ANY WARRANTY; without even the implied warranty of
  18. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  19. GNU General Public License for more details.
  20. You should have received a copy of the GNU General Public License
  21. along with this program. If not, see <https://www.gnu.org./licenses/>.
  22. -->
  23. <!DOCTYPE html>
  24. <html xmlns="http://www.w3.org/1999/xhtml">
  25. <head>
  26. <base href="https://y.st./en/weblog/2015/12-December/25.xhtml" />
  27. <title>An attempt at rooting an unruly device &lt;https://y.st./en/weblog/2015/12-December/25.xhtml&gt;</title>
  28. <link rel="icon" type="image/png" href="/link/CC_BY-SA_4.0/y.st./icon.png" />
  29. <link rel="stylesheet" type="text/css" href="/link/basic.css" />
  30. <link rel="stylesheet" type="text/css" href="/link/site-specific.css" />
  31. <script type="text/javascript" src="/script/javascript.js" />
  32. <meta name="viewport" content="width=device-width" />
  33. </head>
  34. <body>
  35. <nav>
  36. <p>
  37. <a href="/en/">Home</a> |
  38. <a href="/en/a/about.xhtml">About</a> |
  39. <a href="/en/a/contact.xhtml">Contact</a> |
  40. <a href="/a/canary.txt">Canary</a> |
  41. <a href="/en/URI_research/"><abbr title="Uniform Resource Identifier">URI</abbr> research</a> |
  42. <a href="/en/opinion/">Opinions</a> |
  43. <a href="/en/coursework/">Coursework</a> |
  44. <a href="/en/law/">Law</a> |
  45. <a href="/en/a/links.xhtml">Links</a> |
  46. <a href="/en/weblog/2015/12-December/25.xhtml.asc">{this page}.asc</a>
  47. </p>
  48. <hr/>
  49. <p>
  50. Weblog index:
  51. <a href="/en/weblog/"><abbr title="American Standard Code for Information Interchange">ASCII</abbr> calendars</a> |
  52. <a href="/en/weblog/index_ol_ascending.xhtml">Ascending list</a> |
  53. <a href="/en/weblog/index_ol_descending.xhtml">Descending list</a>
  54. </p>
  55. <hr/>
  56. <p>
  57. Jump to entry:
  58. <a href="/en/weblog/2015/03-March/07.xhtml">&lt;&lt;First</a>
  59. <a rel="prev" href="/en/weblog/2015/12-December/24.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2015/12-December/26.xhtml">Next&gt;</a>
  61. <a href="/en/weblog/latest.xhtml">Latest&gt;&gt;</a>
  62. </p>
  63. <hr/>
  64. </nav>
  65. <header>
  66. <h1>An attempt at rooting an unruly device</h1>
  67. <p>Day 00293: Friday, 2015 December 25</p>
  68. </header>
  69. <p>
  70. It occurred to me today that while the <a href="/en/">home page of my main website</a> lists hashes of the site&apos;s <abbr title="Transport Layer Security">TLS</abbr> certificate, these hashes are inaccurate.
  71. The hashes are for the certificate that I used on my own server, but for security reasons, I generated a new certificate when I uploaded the website to <a href="https://wowana.me/">wowaname</a>&apos;s server.
  72. No one has pointed out the bad hashes up through now, so I can only assume that no one is checking the hashes anyway.
  73. I have removed the bad hashes, though I have not added good hashes and might not unless hashes are requested.
  74. </p>
  75. <p>
  76. My mother still has not chosen what she wants done on the mobile front.
  77. I have told her repeatedly that before I can get the mobile that she wants me to carry, she needs to decide which mobile and which plan.
  78. It is clear that the mobile and plan that I chose myself is not good enough for her.
  79. However, she keeps getting on my case about it, still without making a decision.
  80. In an attempt to prevent such future arguments in the future, I purchased a cheap mobile on a cheap plan that has the stupid <abbr title="Short Message Service">SMS</abbr> service that she wants me to have.
  81. To be clear though, even when my Replicant was on a plan with <abbr title="Short Message Service">SMS</abbr> and calling features, it was not good enough for her.
  82. This secondary mobile will only alleviate her most recent gripes.
  83. If she wants me to use exactly the device she chooses, she is going to have to actually choose a device.
  84. Likewise, this device does not meet my needs, and will not in any way be a replacement for my Replicant.
  85. </p>
  86. <p>
  87. I chose the cheapest device I could find, a TracFone LG Optimus Fuel, and put it on the cheapest plan I could find, a $20 <abbr title="United States Dollars">USD</abbr> plan that only needs to be renewed every three months.
  88. This device also has two other useful features, which are that it comes with a small micro<abbr title="Secure Digital">SD</abbr> card and that it is rootable without the use of a Windows machine.
  89. Unfortunately, the only known rooting method I could find for this device requires the use of a proprietary mobile application.
  90. This is certainly not acceptable for my Replicant device, which needs to be free and needs to be trusted, but this secondary device is already burdened by proprietary software and can never be trusted.
  91. By rooting the device, I was at least able to make the device partially behave itself and not spy on me on Google&apos;s behalf as much.
  92. </p>
  93. <p>
  94. Before resorting to the know-to-work rooting method, which requires the use of a proprietary application, I first tried modifying a free solution to meet my needs.
  95. Some software called <a href="http://forum.xda-developers.com/note-2-verizon/general/root-adb-ghettoroot-v0-1-towelroot-port-t2864125">Ghetto Root</a> claims to be a reverse engineering of the proprietary application, though it is only known to work on one device, and it is no the one that I am working with.
  96. Like the proprietary option, Ghetto Root is supposed to install the same proprietary root access manager, so I edited the code to instead try to install <a href="http://koush.com/">Superuser</a>, the free root access manager.
  97. I additionally added the &quot;mod string&quot; appropriate for my device.
  98. The installer claims success, but it seems to actually fail.
  99. After running it, I found a symbolic link at <code>/system/bin/su</code>, but it points to a file that does not exist and I cannot be sure that that symbolic link did not already exist.
  100. Being unable to do this the free way, and the alternative being that I walk around with a spyware-enabled device that offered no privacy or freedom whatsoever, I resorted to temporarily using the proprietary rooter, knowing that once it installed the proprietary root manager, I could swap it out for the free root manager and remove the rooting application.
  101. Before starting, I reset the device for good measure.
  102. </p>
  103. <p>
  104. It is important to note that before starting, I did not activate any mobile plan and did not give the mobile access to my Wi-Fi network.
  105. I could not allow the device to phone home before the process was complete.
  106. I downloaded both the proprietary rooting application, the free <a href="https://f-droid.org/repository/browse/?fdid=com.koushikdutta.superuser">Superuser</a> application, <a href="https://f-droid.org/">F-Droid</a>, <a href="https://f-droid.org/repository/browse/?fdfilter=orbot&amp;fdid=org.torproject.android">Orbot</a>, <a href="https://f-droid.org/repository/browse/?fdfilter=orbot&amp;fdid=org.ethack.orwall">orWall</a>, and the <a href="https://repo.xposed.info/module/de.robv.android.xposed.installer">Xposed Installer</a> on my laptop, not the mobile.
  107. I tried to keep my list of applications to add minimal, but felt that these five applications were justified for the following reasons.
  108. Superuser, orWall, and the Xposed installer all make changes to the <code>/system</code> partition, which on this device, is a pain to modify.
  109. We should be able to modify it once, then forget about it, having our changes survive even when performing a factory reset.
  110. orWall changes the system such that all Internet connectivity is broken unless orWall and a root application are present, so we need orWall and Superuser installed at all times to prevent us from having to look up complicated solutions or reinstall the applications after a system reset.
  111. F-Droid and the Xposed Installer both act as application repositories, and it would be nice to be able to install the applications we want right away instead of having to look for the repository applications first.
  112. (Please be careful about what you install from the Xposed Installer.
  113. It does not commit to keeping its repository stocked with only free applications, so many applications it contains are proprietary.
  114. Still, the application store itself and some of the applications it carries are in fact free.) Lastly, Orbot seemed like a good idea, given that orWall was already in the group.
  115. Without Orbot, orWall and Superuser could still be used to enable clearnet network connectivity, even if just long enough to install Orbot, but why not do things right instead? Why not have the Orbot installation survive system resets so that we can send our traffic through <abbr title="The Onion Router">Tor</abbr> from the start?
  116. </p>
  117. <p>
  118. I went through the Android setup dialog, disabling automatic rotation and networking, but skipping all the input options.
  119. I quickly found that this device does not come with a file manager, making direct installation of packages placed in the file system impossible.
  120. I tried to install the application via <abbr title="Android Debug Bridge">ADB</abbr>, but <abbr title="Android Debug Bridge">ADB</abbr> could not find the device.
  121. I went into the device settings menu and tapped on the &quot;build number&quot; information rapidly until the developer options were enabled, went the the developer options menu, and enabled &quot;<abbr title="Universal Serial Bus">USB</abbr> debugging&quot;.
  122. This fixed the issue, and I was able to install the proprietary rooting application, using a <a href="http://forum.xda-developers.com/showpost.php?s=262b98da09caccb6a61f052ddd650850&amp;p=22547664&amp;postcount=3">command retrieved from a forum</a>.
  123. Using <a href="https://androidarea51.com/all-things-root/working-root-for-lg-optimus-fuel-woot/msg29830/#msg29830">instructions from another forum</a>, I tweaked the settings of the proprietary rooting application and tried to root the device.
  124. However, the rooting application refused to perform without a network connection.
  125. My guess is that the rooting application wants to be able to phone home for statistical purposes.
  126. Being unable to route the connection through <abbr title="The Onion Router">Tor</abbr>, as the device was not rooted yet, I disabled or uninstalled every application that I could aside from the rooting application (so that they would have the smallest chance of phoning home), and am now waiting until I have a chance to use a public Wi-Fi point, turn on the Wi-Fi functionality, and root the device.
  127. It is unfortunate that the rooting application will probably report my hardware information such as the <abbr title="media access control">MAC</abbr> address, as well as an <abbr title="Internet Protocol">IP</abbr> address that pinpoints my city (or rather, the city directly touching my city), but at least it will be unable to get my home <abbr title="Internet Protocol">IP</abbr> address or any sort of telephone number.
  128. While disabling all the applications, I found that supposedly, this device has a file manager, though I cannot find any way to access it.
  129. </p>
  130. <p>
  131. I kind of want to try my hand at creating a <abbr title="The Onion Router">Tor</abbr>-based search engine.
  132. It has been done before, but I see no reason why I cannot build one too.
  133. If I end up gathering too much of an index though, I will probably have to shut it down out of lack of resources.
  134. </p>
  135. <p>
  136. My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
  137. </p>
  138. <hr/>
  139. <p>
  140. Copyright © 2015 Alex Yst;
  141. You may modify and/or redistribute this document under the terms of the <a rel="license" href="/license/gpl-3.0-standalone.xhtml"><abbr title="GNU&apos;s Not Unix">GNU</abbr> <abbr title="General Public License version Three or later">GPLv3+</abbr></a>.
  142. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  143. My address is in the source comments near the top of this document.
  144. This license also applies to embedded content such as images.
  145. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  146. </p>
  147. <p>
  148. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  149. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2015%2F12-December%2F25.xhtml"><abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 5.1</a> specification and uses style sheets that conform to the <a href="http://jigsaw.w3.org./css-validator/validator?uri=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2015%2F12-December%2F25.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  150. </p>
  151. </body>
  152. </html>